chore(main): release 0.2.4 - #12
Closed
github-actions[bot] wants to merge 1 commit into
Closed
Conversation
github-actions
Bot
force-pushed
the
release-please--branches--main
branch
from
September 3, 2026 00:38
5c1802a to
fb34584
Compare
Contributor
|
Closing - this proposed v0.2.4 because release-please could only parse this repo's 3-part-semver tags (v0.2.1-v0.2.3) and missed the 2-part ones (v0.2, v0.3, v0.4, v0.5), anchoring to the wrong baseline. Fixed in a follow-up PR that seeds the version explicitly via manifest mode at 0.5.0. release-please will regenerate this correctly once that lands. |
dconlan
added a commit
that referenced
this pull request
Sep 3, 2026
release-please-action's inline `release-type: simple` mode infers the last release purely from git tags matching strict semver (`MAJOR.MINOR.PATCH`). This repo's real release history uses 2-part tags for several releases (`v0.2`, `v0.3`, `v0.4`, `v0.5`), which release-please can't parse — so it silently anchored to the highest tag it *could* parse (`v0.2.3`) and proposed `v0.2.4` as the next release in #12. That's behind the actual latest release (`v0.5`) and would have collided badly once PR #5's v0.5.1/v0.5.2 work lands, had it merged as-is. Switches to manifest mode (`release-please-config.json` + `.release-please-manifest.json`) so the starting version is explicit rather than inferred, seeded at `0.5.0` to match the real `v0.5` tag — meaning the next `fix:`/`feat:` commit correctly proposes `0.5.1`, matching what PR #5's own README already calls its first tranche. #12 (which proposed `v0.2.4`) has been closed rather than left to self-correct, since release-please won't cleanly reconcile an already-proposed higher version against a corrected lower baseline on its own. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Co-authored-by: Claude Sonnet 5 <noreply@anthropic.com>
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
1 participant
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.2.4 (2026-09-03)
Bug Fixes
This PR was generated with Release Please. See documentation.