Repository navigation
fix(internal-scripts): omit changelog SHA suffixes - #17
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
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.
Generated changelog entries append commit SHA suffixes that add noise to release notes.
Remove the SHA suffix from the shared git-cliff template and update the existing formatting regression test to expect message-only entries. Compact list spacing, breaking-change markers, and PR references in commit messages are preserved. PR #15's existing generated core changelog has been updated to the same output.
Validation:
bun fix:codestyle,bun check:all,bun run test, andbun run buildpassed with Bun 1.4.3 and Node 24. All 20 release integration tests passed. Actual-history previews for core, codegen, env, and files contain no generated SHA suffixes and retain their entries and ordering.