docs: document the Release PR check approval step - #48
Merged
Merged
Conversation
GitHub's June 2026 bot-created pull requests change means the Release PR's workflow runs are created but held until someone with write access approves them. Merging first finalises them as failures with no jobs and no logs, which reads as a broken release. Record the approval step, and correct the older claim that workflows are never triggered for PRs opened by the built-in token.
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.
GitHub's bot-created pull requests change means the Release PR's workflow runs are now created but held until a user with write access approves them. Merging the Release PR first finalises those runs as
failurewith zero jobs and no logs, which reads as a broken release when nothing actually broke.Summary
Test plan