Skip to content

fix: restore NODE_AUTH_TOKEN for npm publish#5

Closed
jim80net wants to merge 1 commit intomainfrom
fix/npm-publish-auth
Closed

fix: restore NODE_AUTH_TOKEN for npm publish#5
jim80net wants to merge 1 commit intomainfrom
fix/npm-publish-auth

Conversation

@jim80net
Copy link
Owner

Summary

  • Re-add NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }} to the publish step in release-please.yml

Problem

npm publish --access public --provenance fails with E404 Not Found because no auth token is provided. The --provenance flag adds build attestation via OIDC but does not replace token-based authentication — npm requires NODE_AUTH_TOKEN to authenticate the publish request.

This was accidentally removed in 2fbbcc8.

Test plan

  • Ensure NPM_TOKEN secret exists in the npm GitHub environment
  • Trigger a release and verify publish succeeds

🤖 Generated with Claude Code

npm does not support OIDC authentication — the --provenance flag only
adds build attestation, it does not replace token-based auth. Without
NODE_AUTH_TOKEN, npm publish returns 404 on the scoped package PUT.

Restore the NPM_TOKEN secret reference so the publish step can
authenticate to the registry.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@jim80net jim80net closed this Mar 15, 2026
@jim80net jim80net deleted the fix/npm-publish-auth branch March 15, 2026 22:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant