Repository navigation
ci: match the previous release rules in release-plz - #54
Merged
Merged
Conversation
feat bumps the minor version even on 0.x (features_always_increment_minor), and only feat, fix, perf, revert, and breaking-change commits trigger a release (release_commits), as with the semantic-release setup that release-plz replaced. Without these, release-plz bumped feat by a patch on 0.x and released on any commit that touched a crate.
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.
This restores the version rules from the semantic-release setup that #51 replaced with release-plz.
Changes
In
release-plz.toml:features_always_increment_minor = true:feat:bumps the minor version even on 0.x, as before. release-plz's default bumps it by a patch while the version is 0.x.release_commits: onlyfeat,fix,perf,revert, and breaking-change commits trigger a release, as before. A breaking change is any type with!or aBREAKING CHANGE:footer. Without this, release-plz releases on any commit that changes a crate, includingchore:,docs:,refactor:, and non-conventional messages, each as a patch.Rules after this PR
feat:fix:,perf:,revert:/Revert "…"type!:or aBREAKING CHANGE:footerchore,docs,style,refactor,test,build,cialoneWhen a release does happen, its size still comes from every commit since the last release, so a
featalongside several chores is a minor bump. One difference from before remains by design: release-plz only counts commits that change a published crate's files, so afix:that touches only docs or CI doesn't release.Testing
I checked the
release_commitspattern against sample messages, covering every row of the table pluschore(release): …, which must not release.