ci: Enable automatic CHANGELOG generation #761
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
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 will enable automatic release PR generation by
release-plz.This includes a semver-checks run to ensure that no breaking checks get released in a minor version bump, and CHANGELOG generation based on the commits merged since the last release, grouped by their conventional commits tag (#734).
PRs marked as breaking (by adding a
!after the tag) will be marked as so in the CHANGELOG, and they will force a major version bump.It is possible to modify the created PR before merging as needed; either to reword parts of the changelog or to override the version bump.