chore(release): keep changelog Contributors in the GitHub Release (h3) - #1760
Merged
Conversation
…he GitHub Release changesets/action builds the GitHub Release body via getChangelogEntry(), which slices from the `## <version>` heading to the next *same-depth* (`##`) heading. A `## Contributors` (h2) was acting as that boundary and getting excluded from the release notes — present in CHANGELOG.md but dropped from the GitHub Release. Demote to `### Contributors` (h3) so it stays inside the extracted body. The in-file boundary logic (/^##\s+\d/) is unaffected. Follow-up to #1753 (merged before this fix landed).
james-elicx
changed the title
james-elicx
enabled auto-merge (squash)
June 5, 2026 13:52
commit: |
Contributor
|
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.
Follow-up to #1753 — this one fix was pushed after that PR merged, so it didn't land.
Problem
changesets/actionbuilds the GitHub Release body viagetChangelogEntry(CHANGELOG.md, version), which slices from the## <version>heading to the next heading of the same depth. The contributor list was written as## Contributors(h2) — the same depth as## 0.1.0— so it acted as the section boundary and got excluded from the GitHub Release (it stayed in the committedCHANGELOG.md, but the release notes were truncated just before it).Verified against changesets/action v1.9.0
getChangelogEntry(boundary = next same-depth heading).Fix
Emit
### Contributors(h3) instead.getChangelogEntryincludes deeper headings, so the list now stays inside the extracted release body. The in-file section-boundary logic (/^##\s+\d/) is unchanged.Testing
vp test run scripts/version.test.ts— 9/9 pass (assertions updated to### Contributors).vp checkclean.🤖 Generated with Claude Code