ci: include build, style, and revert commits in generated release notes#329
Merged
Conversation
Code reviewNo issues found. Checked for bugs and CLAUDE.md compliance. |
Owner
Author
|
Successfully created backport PR for |
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.
Summary
git-cliff omits conventional commits that match no parser, and the parser list covered only feat/fix/docs/perf/refactor/test/chore/ci - every
build:-typed commit (all dependabot dependency bumps among them) and anystyle:/revert:commit was silently dropped from generated release notes. This adds the three missing parsers so the upcoming release notes include the dependency updates shipped in this cycle.Verification
^build,^style,^revert).Backport to v1.0: yes (label) - release notes generate from the releasing branch's cliff.toml, so a future advisory-driven 1.0.x release needs the same parsers.