Seed the changelog backports scaffold when cutting a stable branch - #14744
Merged
Conversation
A stable branch's changelog needs the `# v{next} backports` heading
(with `## In this release` / `## In previous releases`) plus a
`# v{this} changes` wrapper so backported PRs have a place to land and
the monthly patch release has entries to demote. The current stable
v1.10 branch was cut without that scaffold, so a backport had nowhere
correct to go and risked being mis-filed under the frozen
`## Regression fixes` (which tracks the previous version's own release
fixes, not backports).
Add the seed step to the branch-creation checklist, and make the
backport checklist, the stable patch-release checklist, and the
changelog rule all reference the scaffold explicitly so the section
names stay consistent across docs.
Collaborator
✅ Snyk checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
cderv
added a commit
that referenced
this pull request
Jul 31, 2026
Cutting and patching the v1.10 stable release surfaced a batch of release-checklist and backport-doc improvements that landed on main: pre-branch checks, merge-step learnings, the changelog backports-scaffold convention (#14744), and the /make-release skill. The v1.10 branch is the one these docs are exercised on when backporting and cutting patch releases, so bring its copies in step with main rather than leaving them frozen at branch-cut.
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
2 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.
While backporting #14742 to the v1.10 stable branch, the changelog entry had nowhere correct to land. Stable branches carry a
# v{next} backportssection to hold backported entries (v1.9 has# v1.10 backports), but v1.10 was cut without it — so the entry would otherwise be mis-filed under## Regression fixes, a frozen section that tracks the previous version's own release fixes, not backports.The scaffold was missing because nothing in the release process seeds it. This adds a branch-cut step to create it, and aligns the backport checklist, the stable patch-release checklist, and the changelog rule so they all refer to the same sections.