Use the versions bot's ruleset bypass when merging - #1223
Merged
Conversation
ewdurbin
marked this pull request as ready for review
August 19, 2026 13:44
jjhelmus
approved these changes
Aug 19, 2026
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.
Summary
Use
gh pr merge --squash --adminwhen merging the versions bot's release-manifest PR. Theversionsruleset requires human review but grantsastral-versions-bota pull-request-only bypass. Plaingh pr mergestops at its blocked-PR preflight check instead of attempting the merge with that permission.This completes the workflow-side change for https://github.com/astral-sh/github-policies/pull/31 and https://github.com/astral-sh/github-policies/pull/34. The failure was observed in astral-sh/versions#163 (release job).