chore(release): pin the bootstrap release version to 0.1.0 - #21
Merged
Merged
Conversation
With no prior tag, release-please treats the repo as a bootstrap and defaults the first release to 1.0.0 regardless of the manifest. initial-version pins that first release to 0.1.0; it has no effect after the first release exists. Co-Authored-By: Claude Fable 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.
Summary
Follow-up to #19: with no prior tag, release-please ignores the
0.0.0manifest at bootstrap and defaulted the first release PR (#20) to 1.0.0.initial-version: 0.1.0pins the bootstrap release; it is inert once a release exists. On merge, release-please regenerates #20 as v0.1.0 (same changelog).🤖 Generated with Claude Code