Skip to content

Conversation

@jkebinger
Copy link
Contributor

Summary

  • Removed the NPM_AUTH_TOKEN environment variable from the release workflow
  • This token is no longer needed since we're using npm trusted publishing with provenance

Details

The workflow already has the necessary configuration for trusted publishing:

  • id-token: write permission for OIDC authentication
  • --provenance flag in the publish command

With 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

Now using npm trusted publishing with provenance, so the NPM_AUTH_TOKEN environment variable is no longer needed. The workflow already has the necessary permissions (id-token: write) and uses the --provenance flag for secure publishing.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
Copy link
Contributor

@jdwyah jdwyah left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thanks!

@jkebinger jkebinger merged commit e5ea956 into main Nov 20, 2025
1 check passed
@jkebinger jkebinger deleted the remove-npm-auth-token branch November 20, 2025 22:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

3 participants