ci(release): use only the new version's changelog entry as release notes - #73
Merged
jdhughes-dev merged 1 commit intoAug 3, 2026
Merged
Conversation
The whole changelog file was passed as the release notes, so every release page repeated the history of the ones before it. Take the entry for the version being released and stop at the next heading, and fail the job if that entry is missing.
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.
The whole changelog file was passed to
gh release create, so each release page repeated the history of every release before it. The notes are now the entry for the version being released, taken from its heading up to the next one, and the job fails if that entry is missing.The v1.2.0 release page has been trimmed the same way.