Fix create-release workflow token - #18
Merged
Merged
Conversation
Use PAT_GITHUB_TOKEN secret instead of github.token, because the default GITHUB_TOKEN doesn't trigger other workflows (GitHub security feature). This ensures the publish workflow runs after a release is created. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
martijnbots
force-pushed
the
fix/create-release-token
branch
from
March 20, 2026 12:27
ef8dc6a to
82a6cd1
Compare
pvdspek
approved these changes
Mar 31, 2026
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
2 participants
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
secrets.GLOBAL_ACTION_TOKENwithgithub.token(the secret is not configured for this repo)contents: writepermission for creating releasesSame fix as bluebillywig/bb-sapi-node-sdk#3.
Test plan
🤖 Generated with Claude Code