fix: use PAT for release-please so release PR triggers required check#21
Merged
Conversation
The default GITHUB_TOKEN cannot trigger pull_request workflows (GitHub loop-prevention), so the release PR never got a `zizmor` run and stayed permanently BLOCKED under branch protection. Pass RELEASE_PLEASE_TOKEN (a fine-grained PAT scoped to this repo: contents + pull-requests write) to the action and the auto-merge step so the release PR triggers zizmor and can auto-merge on green. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.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.
Why
Follow-up to #19. The first release-please run created the release PR with the default
GITHUB_TOKEN. By GitHub's loop-prevention design, a PR opened byGITHUB_TOKENdoes not triggerpull_requestworkflows — so the requiredzizmorcheck never ran on the release PR and it sat permanentlyBLOCKED, unable to auto-merge.Fix
Pass
RELEASE_PLEASE_TOKEN(fine-grained PAT scoped to this repo: contents + pull-requests write) to:release-please-actiontoken:input — so its release PR triggerszizmorghstep — consistent identity with pull-request writeNow the release PR runs
zizmor, goes green, and auto-merges for patch/minor bumps; major bumps stay open for manual approval.Stale release PR #20 (opened by
GITHUB_TOKEN, no checks) was closed; after this merges, release-please opens a fresh release PR via the PAT.🤖 Generated with Claude Code