Repository navigation
ci: request workflows permission for the release token - #399
Merged
Merged
Conversation
The release-create probe returned 422, so the app token can create releases, yet release-please still fails with "Resource not accessible by integration". GitHub listed contents+workflows as an accepted permission set, and 1.21.1 is the first release since v1.20.1 whose commits change .github/workflows/ (#395). Request workflows: write explicitly: if the app has it, the release goes through; if not, token creation fails and names the missing permission. Removes the probe.
jhcipar
approved these changes
Oct 30, 2026
justinwlin
approved these changes
Oct 30, 2026
This was referenced Oct 30, 2026
2 of 4 tasks
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
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 #398. The probe returned:
So the release app's token can create releases on this repo, but release-please still failed right after with
Resource not accessible by integration.Likely cause (not yet confirmed)
The 1.21.1 tag covers #395, which edits a workflow file. It is the only commit since v1.21.0 that touches
.github/workflows/. GitHub requires theworkflowspermission for some ref operations over workflow changes, and the header listscontents=write,workflows=writeas an accepted set. runpod/host's v2.276.4 release with the same app worked tonight, and its range touched no workflow files.One fact cuts against it: v1.20.0 and v1.20.1 both included workflow changes and released with this app. The theory holds only if the app had the Workflows permission then and lost it since.
Change
contents,issues,pull-requestsandworkflowswrite explicitly. Listing permissions limits the token to those, which covers what release-please uses (tags/releases, PR labels and comments).Outcome after merge
Test plan
make quality-checkpasses locallyworkflows🤖 Generated with Claude Code