ci(release): Append commit-based changelogs to release notes - #19
Merged
Conversation
philprime
marked this pull request as ready for review
September 13, 2026 16:01
philprime
enabled auto-merge (squash)
September 13, 2026 16:01
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.
Append a git-cliff commit-based changelog to the existing stable and development release templates. Version tags define the changelog boundaries, while development builds include unreleased commits and ignore the rolling
latesttag. Add git-cliff to the Brewfile for local verification.Verification
Passed
make test,make analyze, andmake build. Local checks verified the exact commit ranges for first, tagged, and development releases and confirmed both templates remain intact with rendered metadata and appended changelogs.