Conversation
|
🎉 This PR is included in version 1.0.3 🎉 The release is available on: Your semantic-release bot 📦🚀 |
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
There was a problem hiding this comment.
This is the final PR Bugbot will review for you during this billing cycle
Your free Bugbot reviews will reset on January 9
Details
You are on the Bugbot Free tier. On this plan, Bugbot will review limited PRs each billing cycle.
To receive Bugbot reviews on all of your PRs, visit the Cursor dashboard to activate Pro and start your 14-day free trial.
| env: | ||
| GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} | ||
| HUSKY: 0 | ||
| NPM_CONFIG_PROVENANCE: true |
There was a problem hiding this comment.
Missing NODE_AUTH_TOKEN for npm authentication
The registry-url configuration in actions/setup-node creates an .npmrc file that expects NODE_AUTH_TOKEN for authentication. However, the "Publish to npm" step's environment only includes GITHUB_TOKEN and HUSKY - no NODE_AUTH_TOKEN is provided. This will likely cause npm publishing to fail with authentication errors since the generated .npmrc references an undefined token variable.
Additional Locations (1)
1 participant
Note
Modernizes the release pipeline and aligns it with npm OIDC provenance requirements.
actions/checkoutandactions/setup-nodetov4; pins Node to22.14NPM_CONFIG_PROVENANCEenv and continues publishing viasemantic-releaseWritten by Cursor Bugbot for commit f92beda. This will update automatically on new commits. Configure here.