ci: use granular NPM token for publishing#33
Closed
satoshai-dev wants to merge 2 commits intomainfrom
Closed
Conversation
Drop NPM_TOKEN secret in favor of OIDC-based provenance publishing. Requires Trusted Publishing to be configured on npmjs.com. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Trusted Publishing with changesets/action doesn't work out of the box. Use a granular npm token with 2FA bypass instead. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
satoshai-dev
changed the title
Owner
Author
|
No-op — workflow already uses NPM_TOKEN. Just needed a granular token in repo secrets. |
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
NPM_TOKENsecretNPM_TOKENin repo secrets🤖 Generated with Claude Code