fix(ci): drop RELEASE_PAT — use default GITHUB_TOKEN#20
Merged
Conversation
The release job's checkout was passing `token: ${{ secrets.RELEASE_PAT }}`,
but no such secret exists in this repo. With the input resolving to an empty
string, git auth setup wrote `AUTHORIZATION: basic ` (empty value), then the
fetch step prompted for a username and aborted with `terminal prompts disabled`.
Drop the explicit token. The job already declares `permissions: contents: write`
+ `id-token: write`, so the default `GITHUB_TOKEN` is sufficient for the
chore(release) commit + tag push and OIDC continues to handle npm publish.
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.
Why
The release job's checkout passed
token: \${{ secrets.RELEASE_PAT }}, but no such secret exists in this repo. With the input resolving to an empty string, the auth setup wroteAUTHORIZATION: basic(empty value), thengit fetchprompted for a username and aborted withterminal prompts disabled. This blocked v0.3.1 release in run 25018407875.Fix
Drop the explicit
token:line. The release job already declares:```yaml
permissions:
contents: write # for the chore(release) commit + tag push to main
id-token: write # for npm OIDC provenance
```
so the workflow-issued
GITHUB_TOKENis sufficient for the git push, and OIDC continues to handle npm publish (no NPM_TOKEN needed).Test plan