chore(release): force first release to 0.1.0 (release-as)#35
Merged
Conversation
release-please bootstraps a 0.0.0 / no-prior-release baseline to 1.0.0 for the first release; release-as pins it to 0.1.0 to match the documented pre-1.0 strategy. Remove this line after v0.1.0 ships so 0.2.0+ compute from commits. Signed-off-by: Sam Gammon <sam@elide.dev>
There was a problem hiding this comment.
Pull request overview
Pins the next Release Please–generated release to 0.1.0 to align the repository’s initial pre-1.0 release strategy (avoiding the default bootstrap to 1.0.0 when no prior tag exists).
Changes:
- Add
release-as: "0.1.0"to the Release Please package configuration to force the next computed release version.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Merging this PR will not alter performance
|
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
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.
One-line fix for the version computed on PR #34.
release-please opened #34 as 1.0.0 — its first-release bootstrap defaults a
0.0.0/no-prior-tag baseline to1.0.0(thebump-*-pre-majorflags only affect subsequent bumps).release-as: "0.1.0"pins the next release to 0.1.0, matching the documented pre-1.0 strategy.Once this merges, the
releaseworkflow re-runs and release-please regenerates #34 wholesale at 0.1.0 (title, body metadata, label, manifest, changelog) — so the merge will tagv0.1.0.Remove this line after v0.1.0 ships so
0.2.0+ compute from Conventional Commits again.