Repository navigation
ci: use the built-in GITHUB_TOKEN instead of FRONTEND_GH_TOKEN - #1140
Merged
Merged
Conversation
FRONTEND_GH_TOKEN is no longer available to this repo, so Canary fails with "GitHub token not found". Use the built-in token and grant the jobs the permissions auto needs. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Move GH_TOKEN, NPM_TOKEN and NPM_CONFIG_PROVENANCE out of the workflow-level env block and onto the auto steps. Install and build steps no longer see the tokens. Give the Publish build job explicit read-only permissions. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
auto reads GH_TOKEN or GITHUB_TOKEN for the API, and uses GITHUB_TOKEN (with the x-access-token prefix) for git pushes in Actions. GH_TOKEN was redundant. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
josh-payward
approved these changes
Nov 10, 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
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 Canary job on #1139 failed with
GitHub token not foundbecausesecrets.FRONTEND_GH_TOKENresolved to an empty string. The secret worked on 2026-10-20 and is no longer in the list of org secrets visible to this repo.What
canary.yml:GH_TOKENnow usessecrets.GITHUB_TOKEN. The Canary job getspull-requests: writesoauto canarycan comment on the PR.publish.yml:GITHUB_TOKENandGH_TOKENnow usesecrets.GITHUB_TOKEN. Thetoken:override on both checkouts is removed. The Publish job getscontents: write,pull-requests: writeandissues: writesoauto shipitcan push the release commit and tags and comment on or label released PRs.Risks to check before merging
masterbranch protection requires PRs or blocks pushes bygithub-actions[bot], the release step will fail when it pushes the version bump. The old token likely got around this.After this merges, #1139 needs a rebase or re-run to get a green Canary.
🤖 Generated with Claude Code
📦 Published PR as canary version:
Canary Versions✨ Test out this PR locally via:
npm install @magic-ext/bitcoin@29.4.1-canary.1140.42878562125.0 # or yarn add @magic-ext/bitcoin@29.4.1-canary.1140.42878562125.0