chore(main): release wavekat-com 0.0.64 - #182
Merged
wavekat-eason merged 2 commits intoSep 7, 2026
Merged
Conversation
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
changed the title
Contributor
Author
wavekat-eason
deleted the
release-please--branches--main--components--wavekat-com
branch
September 7, 2026 11:01
Contributor
Author
|
🤖 Created releases: 🌻 |
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
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🤖 I have created a release beep boop
0.0.64 (2026-09-07)
Features
This PR was generated with Release Please. See documentation.
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 withbump-minor-pre-majorunset, 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. TheBREAKING CHANGESsection 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.jsonsetsbump-patch-for-minor-pre-majorbut notbump-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