Repository navigation
ci: open a release PR only for user-facing commits - #3
Merged
Merged
Conversation
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-plz opened #2 (v0.1.1) for the release automation commit alone. That commit is
ci:, which the changelog skips, so #2 had no 0.1.1 entry and its body fell back to the 0.1.0 notes. Merging it would have published v0.1.1 with 0.1.0's release notes.This sets
release_commitsso that onlyfeat,fix,perf,refactor,docsandrevertcommits (including the!breaking forms) make a release.Checked locally with release-plz 0.3.170: on this branch
updateproposes nothing, and with afix(guard):commit added it proposes 0.1.0 -> 0.1.1 with a Fixed entry.