ci: use a bee-runner App token for release-please - #531
Merged
Conversation
GHA_PAT_ADVANCED holds a dead token (401 Bad credentials). Mint a short-lived bee-runner App token scoped to this repo instead, with contents, pull-requests and issues write.
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_github.yamlhas been broken since at least 17 Aug because ofBad credentials. TheGHA_PAT_ADVANCEDorg secret is no longer working. It was shared with this repo correctly; the stored token itself is dead. This is the same fix as bee-docs#843.This change creates a short-lived token from the
bee-runnerApp. It works only on this repo and can read and write contents, pull requests, and issues. We need theissuespermission for release-please'sautorelease:labels.We use an App token instead of
GITHUB_TOKENbecause thepublish_*workflows run when areleaseis created.GITHUB_TOKENreleases don't trigger this event.