chore: remove NPM_AUTH_TOKEN from release workflow #19
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
Details
The workflow already has the necessary configuration for trusted publishing:
id-token: writepermission for OIDC authentication--provenanceflag in the publish commandWith trusted publishing, npm authenticates the workflow using GitHub's OIDC tokens instead of requiring a stored NPM_AUTH_TOKEN secret. This is more secure and eliminates the need to manage and rotate tokens.
🤖 Generated with Claude Code