build: pin the initial release to 0.1.0 - #3
Merged
Conversation
release-please treats a 0.0.0 manifest as 'no release yet' and defaults the first release to 1.0.0, which overrides bump-minor-pre-major. A shell extension that has never been through an install, upgrade or reboot test must not ship as 1.0.0.
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 proposed 1.0.0 for the first release (see #2). It treats a 0.0.0 manifest as 'no release yet' and applies its default initial version, which takes precedence over
bump-minor-pre-major.initial-version: 0.1.0pins it. 1.0.0 would claim a stability this project explicitly does not have — the installer has never been run, and there has been no reboot or sign-out testing.