docs(release): replace future planning sections with actionable checklist steps#85
Merged
vitormattos merged 1 commit intomainfrom Apr 6, 2026
Merged
Conversation
…list steps Remove the 'Automation candidates' and 'Suggested future helper commands' sections, which described potential improvements rather than concrete steps. Absorb the two genuinely actionable items directly into the checklist: - Add a git ls-remote command to confirm the stable branch HEAD SHA before creating the GitHub release tag. - Add a gh api command to verify the milestone was correctly renamed from 'Next Patch (XX)' to the versioned title before writing the release body. Signed-off-by: Vitor Mattos <1079143+vitormattos@users.noreply.github.com>
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.
Remove the 'Automation candidates' and 'Suggested future helper commands' sections, which described potential improvements rather than concrete steps to follow.
Absorb the two actionable items directly into the checklist:
git ls-remotecommand to confirm the stable branch HEAD SHA before creating the GitHub release tag.gh apicommand to verify the milestone was correctly renamed fromNext Patch (XX)to the versioned title before writing the release body.