fix: set initial-version so the first release is v0.0.1 - #3
Merged
Merged
Conversation
release-please proposed 1.0.0 for the first release. The bump flags do not apply to it: bump-patch-for-minor-pre-major is documented as "feature changes only bump semver patch if version < 1.0.0", so it governs bumping *from* an existing version - and there is no existing version yet. A 0.0.0 manifest entry is not treated as a released version either, so release-please fell back to its default first release of 1.0.0. initial-version is the option that covers this case: "releases the initial library with a specified version". The bump flags stay - they are still what keeps subsequent feature releases on 0.0.x rather than jumping to 0.1.0. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01NiwgsqcQ4JikhFYj4NHEjM
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.
release-please opened #2 proposing 1.0.0. It should be 0.0.1.
Why it happened
My config set the bump flags but not
initial-version. Per the schema:bump-patch-for-minor-pre-majorinitial-versionThe bump flags govern bumping from an existing version — and there isn't one yet. A
0.0.0entry in.release-please-manifest.jsonisn't treated as a released version either, so release-please fell back to its default first release of 1.0.0.I had assumed the manifest plus the bump flags would be enough. They aren't;
initial-versionis the option that covers a first release.The fix
The bump flags stay — they're still what keeps later feature releases on
0.0.xrather than jumping to0.1.0.After merging
release-please will recompute #2 as
chore(main): release 0.0.1. Merging that tagsv0.0.1and the build workflow publishesghcr.io/glueops/toolbox:0.0.1,:0.0and:latest, multi-arch.If #2 doesn't update on its own, closing it will make release-please reopen it on the next push to
main.