chore: remove NPM_TOKEN secret, use trusted publisher #26
Conversation
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
The workflow is already configured for NPM trusted publisher with: - id-token: write permission (required for OIDC) - --provenance flag on npm publish commands This removes the now-unnecessary NPM_TOKEN environment variable. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
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.
Summary
NPM_TOKENenvironment variable from the release workflowDetails
The release workflow already has all the necessary configuration for trusted publisher:
id-token: writepermission (required for OIDC)--provenanceflag onnpm publishcommandsThe
NPM_TOKENsecret is no longer needed and can be safely removed from GitHub Secrets after this PR is merged.References
🤖 Generated with Claude Code