fix: Use release-as to target v1.0.0 instead of editing manifest#203
Merged
jarfernandez merged 1 commit intomainfrom Mar 16, 2026
Merged
fix: Use release-as to target v1.0.0 instead of editing manifest#203jarfernandez merged 1 commit intomainfrom
release-as to target v1.0.0 instead of editing manifest#203jarfernandez merged 1 commit intomainfrom
Conversation
The manifest tracks the current released version (0.21.1), not the target. Setting it to 1.0.0 made release-please think 1.0.0 was already released, causing `feat!:` to bump to 2.0.0. The correct approach is `"release-as": "1.0.0"` in the config, which forces the next release to that exact version. Remove `release-as` after the 1.0.0 release.
This was referenced Mar 16, 2026
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.
Summary
1.0.0back to0.21.1(the actual current released version)"release-as": "1.0.0"to.github/release-please-config.jsonto force the next release to v1.0.0The manifest tracks the current released version, not the target. Setting it to
1.0.0made release-please think 1.0.0 was already released, so thefeat!:breaking change bumped to 2.0.0.Note: Remove
"release-as": "1.0.0"from the config after the v1.0.0 release so subsequent releases use normal semver bumping.Test plan
autorelease: pendingtoautorelease: tagged🤖 Generated with Claude Code