[HowardBraham]

Explanation

merge-previous-releases restores a finalized release's changelog section and link reference after the git merge -s ours, but left [Unreleased]: …/compare/vX...HEAD pointing at the older release it started from. The next changelog update then lists a compare range that includes the restored release.

The script now moves the [Unreleased] link to the restored version when that version is newer than the link's start. The link is left alone when it is missing, ambiguous, not a compare/vX.Y.Z...HEAD link, or already newer.

Testing

• Two new unit tests in merge-previous-releases.test.mts.
• Ran the real merge-previous-releases action from a fork workflow: the destination's [Unreleased] link changed from v8.0.9...HEAD to v8.1.0...HEAD, and the destination's own unreleased entry was kept.

---

Note

Low Risk
Scoped to release changelog merge automation with conservative no-op guards; no runtime or auth impact.

Overview
Fixes merge-previous-release-changelog so after it restores a finalized release section, the [Unreleased] GitHub compare link (…/compare/vX.Y.Z...HEAD) starts from that restored version when it is newer than the link’s current base. Missing, ambiguous, non-standard, or already-newer links are left unchanged.

main now runs this step after inserting the release reference. Two integration tests cover the forward move and the no-op when the destination already points at a newer release. CHANGELOG documents the fix under Unreleased.

^{Reviewed by Cursor Bugbot for commit f971353. Bugbot is set up for automated code reviews on this repo. Configure here.}

Related PRs

• github-tools #327: add-team-label falls back to team-bots for bot accounts
• Extension #47954 and Mobile #39756: stop maintaining per-bot lists in the client repos