Skip to content

feat!: drop the Early tag from the Windows download rows - #181

Merged
wavekat-eason merged 1 commit into
mainfrom
claude/remove-early-items-8c19yh
Sep 7, 2026
Merged

feat!: drop the Early tag from the Windows download rows#181
wavekat-eason merged 1 commit into
mainfrom
claude/remove-early-items-8c19yh

Conversation

@wavekat-eason

Copy link
Copy Markdown
Contributor

Windows is no longer younger than the other two platforms, so the EARLY pill it carried on every Windows download row no longer says anything true. This removes it everywhere.

What changed

  • VoiceDownloadRow.astro — removes both renders of the tag: the one riding the label on the direct .exe rows, and the one that moved under the requirement line on the Microsoft Store badge row (a badge row has no label to annotate). The tagCls pill style goes with them, and with no string left to read the component no longer takes a ui prop.
  • VoiceDownload.astro / VoiceDownloadAll.astro — drop the now-unused ui prop from their VoiceDownloadRow calls. Both still use ui themselves.
  • i18n.ts + src/lib/ui/*.ts — removes dlEarly from UIStrings and from all nine locales (Early, 早期版本, 早期版, 초기 버전, Früh, Inicial, Débuts, Iniziale).

What deliberately stayed

  • DownloadGroup.windows. It still selects the unsigned-download note under the Windows column — a separate claim that is still accurate — so the flag stays and only its doc comment changes.
  • Every "early access" mention elsewhere on the site. Those are about Pro being free during early access, not about the Windows build's maturity, and are untouched.

Verification

  • npm run build — 231 pages, 189 OG cards, clean.
  • npm run check:links — 231 pages scanned, no broken or leaking internal links (2 /docs/voice/* links skipped: the private docs sync needs SYNC_DOCS_TOKEN, unavailable here).
  • npm run check:meta — within budget; the 22 short-description warnings are pre-existing and untouched by this change, which alters no title or description.
  • npm test — 5 passed.
  • Grepped dist/**/voice/download/index.html across all nine locales: no EARLY in any translation, while the store badges, all five download rows and the unsigned-download note are still rendered.

The claude-seo skills this repo asks for on page edits aren't available in this session; since the change touches no title, description, heading or body copy, the meta/link gates above are the only signals it moves.

🤖 Generated with Claude Code

https://claude.ai/code/session_01Gtr5DLgddkeyaC3cHUQqgb


Generated by Claude Code

Windows is no longer younger than the other two platforms, so the "Early"
pill it carried on every download row — the label pill on the direct .exe
rows and the one under the Microsoft Store badge — no longer says anything
true.

Removes both renders, the now-unused `tagCls`, and `dlEarly` from
`UIStrings` and all nine locales. `DownloadGroup.windows` stays: it still
selects the unsigned-download note under the Windows column, which is a
separate and still-accurate claim. With no string left to read,
`VoiceDownloadRow` no longer takes a `ui` prop.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Gtr5DLgddkeyaC3cHUQqgb
@github-actions

github-actions Bot commented Sep 6, 2026

Copy link
Copy Markdown
Contributor

@wavekat-eason
wavekat-eason marked this pull request as ready for review September 7, 2026 10:39
@wavekat-eason
wavekat-eason merged commit e2d5f98 into main Sep 7, 2026
2 checks passed
@wavekat-eason
wavekat-eason deleted the claude/remove-early-items-8c19yh branch September 7, 2026 10:40
wavekat-eason pushed a commit that referenced this pull request Sep 7, 2026
Retarget the release from 1.0.0 to 0.0.64.

The 1.0.0 came from one mislabelled commit, not from a decision to ship
1.0: #181 removed the Early tag from the Windows download rows and was
titled `feat!:`, and with `bump-minor-pre-major` unset, release-please
reads a pre-1.0 breaking change as the 1.0.0 promotion. Removing a badge
is neither breaking nor a milestone, so the version follows the change:
a patch.

Also drops the BREAKING CHANGES section from the entry, which the `!`
generated and which would otherwise contradict the version beside it.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Gtr5DLgddkeyaC3cHUQqgb
wavekat-eason pushed a commit that referenced this pull request Sep 7, 2026
🤖 I have created a release *beep* *boop*
---


##
[0.0.64](wavekat-com-v0.0.63...wavekat-com-v0.0.64)
(2026-09-07)


### Features

* drop the Early tag from the Windows download rows
([#181](#181))
([e2d5f98](e2d5f98))

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).

---

**Retargeted from 1.0.0 to 0.0.64 — see 368786d.** The 1.0.0 came from
one mislabelled commit rather than a decision to ship 1.0: #181 removed
the EARLY tag from the Windows download rows and was titled `feat!:`,
and with `bump-minor-pre-major` unset, release-please reads a pre-1.0
breaking change as the 1.0.0 promotion. Removing a badge is neither
breaking nor a milestone, so the version follows the change: a patch.
The `BREAKING CHANGES` section the `!` generated is dropped with it,
since it would otherwise contradict the version beside it.

Both the PR body above and the branch files were edited, because
release-please parses the released version out of this body on merge and
the tag would otherwise still read `wavekat-com-v1.0.0`.

Follow-up, separately: `release-please-config.json` sets
`bump-patch-for-minor-pre-major` but not `bump-minor-pre-major`, so
CLAUDE.md's "`feat!:` → minor bump (pre-1.0)" is not what the config
actually does today — it jumps to 1.0.0. One of the two should move.

_Generated by [Claude Code](https://claude.ai/code)_

---------

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Claude <noreply@anthropic.com>
wavekat-eason pushed a commit that referenced this pull request Sep 7, 2026
The first draft claimed the squash always drops the body. #181 did land
as its title alone, but #182 kept its body — so the honest rule is that
what survives beyond the title varies with how the PR is merged, which
is itself the reason a version override must not live there.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Gtr5DLgddkeyaC3cHUQqgb
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants