ci: use org release-bot app token for release-please#4
Merged
Conversation
PRs opened with the default GITHUB_TOKEN don't trigger workflows, so the required validate check never ran on release PRs. Mint a token from the org's release-bot GitHub App instead — same pattern as bifrost-mkdocs, json-api-toolkit, and hashicorp-vault-backup. Co-Authored-By: Claude Fable 5 <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.
Release PRs created with the default
GITHUB_TOKENdon't trigger other workflows (GitHub's recursion guard), so the requiredvalidatecheck never ran on them and they sat blocked until a manual close/reopen.This adopts the org-standard fix used by
bifrost-mkdocs,json-api-toolkit, andhashicorp-vault-backup: mint a token from the release-bot GitHub App (vars.RELEASE_BOT_APP_ID+secrets.RELEASE_BOT_PRIVATE_KEY, both already exposed to this repo) and pass it to release-please. PRs it opens then trigger CI like any user's.Dropped the now-unused
permissionsblock — the app token replacesGITHUB_TOKENentirely.ci:commit, so this doesn't affect the pending 0.2.0 release PR's contents.🤖 Generated with Claude Code