🔧 chore(ci): auto-stamp release-notes heading + add Full Changelog link#388
Merged
Merged
Conversation
The release-cut "Generate release notes" step copied the CHANGELOG section verbatim. For pre-releases cut before the CHANGELOG was stamped, the [Unreleased] fallback leaked a literal "## [Unreleased]" heading (no version, no date) into the published GitHub Release — this hit rc.17, rc.18, rc.19, and rc.25. - When the [Unreleased] fallback is used, rewrite the section heading in the generated notes to "## [<version>] — <date>" so a cut can never again publish an unstamped heading. CHANGELOG.md itself is still stamped separately at release time. - Prepend a "Full Changelog" compare link (previous tag → this tag) to every release's notes, resolved from the newest existing release.
s-b-e-n-s-o-n
requested review from
ALARGECOMPANY and
biggest-littlest
as code owners
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
biggest-littlest
approved these changes
May 22, 2026
Member
biggest-littlest
left a comment
biggest-littlest
left a comment
There was a problem hiding this comment.
✅ Reviewed — release-cut hardening. Auto-stamp prevents the [Unreleased] heading leak; Full Changelog link is a clean addition. zizmor green. Approving.
ALARGECOMPANY
approved these changes
May 22, 2026
Member
ALARGECOMPANY
left a comment
ALARGECOMPANY
left a comment
There was a problem hiding this comment.
✅ Second approval — workflow-only, no history rewrite, all gates green. LGTM.
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
3 participants
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.
Hardens the
release-cut.yml"Generate release notes from changelog" step so a cut can never publish an unstamped heading, and adds a compare link to every release.Background
The release-notes step copied the CHANGELOG section verbatim. For pre-releases cut before the CHANGELOG
[Unreleased]section was renamed to its versioned heading, the fallback leaked a literal## [Unreleased]heading — no version, no date — into the published GitHub Release. This hit rc.17, rc.18, rc.19, and rc.25 (all four release bodies have since been corrected by hand).Changes
[Unreleased]fallback is used, the section heading in the generated notes is rewritten to## [<version>] — <date>. A cut can no longer ship an unstamped heading.CHANGELOG.mditself is still stamped separately at release time — this only touches the published release body.**Full Changelog**: …/compare/<prev>...<this>, with the previous tag resolved from the newest existing release (the current tag isn't pushed yet at notes-generation time).Scope
Workflow-only, future releases only — no existing release history is rewritten. Verified:
actionlint/qlty,zizmor(no findings), and the full pre-push gate pass.