fix(release): use organization token for release PR - #171
Merged
Conversation
Teakowa
marked this pull request as ready for review
August 18, 2026 11:17
github-project-automation
Bot
moved this from Backlog
to Done
in Make Workshop Great Again
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.
Summary
GH_TOKENsecret asGITHUB_TOKENfor release-please;Root cause
The first post-merge run used the workflow's built-in
github.token, and GitHub rejected release-please's pull request creation withGitHub Actions is not permitted to create or approve pull requests.Validation
github.tokenreference;token: ${{ secrets.GH_TOKEN }}andGITHUB_TOKEN: ${{ secrets.GH_TOKEN }}are present;git diff --check.Observed failure: https://github.com/wrightkit/wright/actions/runs/32125755240/job/95675823524
Refs #169