Repository navigation
chore: keep release-please inside the 0.x series - #15
Merged
Merged
Conversation
By default release-please reads the "!" on a breaking change as a graduation to 1.0.0, which is what #14 proposed. This is still a 0.x gem, so a breaking change should take the minor and an ordinary feature should take the patch. Signed-off-by: Tim Smith <tsmith84@proton.me>
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 read the `feat!` in #13 as a graduation and opened #14 proposing
1.0.0. busser-bash is still a 0.x gem, so a breaking change should take the minor
(0.1.4 -> 0.2.0) rather than jumping to 1.0.
Adds `bump-minor-pre-major` and `bump-patch-for-minor-pre-major`. Once this
merges, #14 should be closed so release-please regenerates it at 0.2.0.
The same setting is on the five sibling pull requests.