Repository navigation
Conversation
Runs triggered by GITHUB_TOKEN on the release PR wait for maintainer approval. Use the RELEASE_PLEASE_TOKEN secret when set, falling back to GITHUB_TOKEN.
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.
Why
The release PR is opened by release-please with
GITHUB_TOKEN, so itsBuild and releaserun stays in action_required ("1 workflow awaiting approval") until a maintainer approves it.What
release-please-actionusessecrets.RELEASE_PLEASE_TOKEN, falling back togithub.tokenwhen the secret is missing (current behaviour).To do after merge
Create the
RELEASE_PLEASE_TOKENrepository secret. The next release-please update of the release PR will then trigger its build without approval.Tag pushes stay inert: the workflow only listens to
pull_requestand pushes tomain.