Sync release-process docs from main - #14745
Merged
Merged
Conversation
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.
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. |
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.
Follow-up to #14744. The v1.10 branch's release and backport docs were frozen at branch-cut, while
maingained a batch of improvements the v1.10 release itself surfaced — pre-branch checks, merge-step learnings, the changelog backports-scaffold convention, and the/make-releaseskill. These docs are exercised on the stable branch when backporting and cutting patch releases, so this brings v1.10's copies to parity with main.