The v1.1.0 release workflow reached npm publish on commit 066597f after package gates passed, but failed with ENEEDAUTH because NODE_AUTH_TOKEN was empty.
Evidence:
- Workflow: Publish to npm, run 26001744009
.github/workflows/publish.yml uses ${{ secrets.NPM_TOKEN }}
- GitHub logs show
NODE_AUTH_TOKEN: empty
- Local
npm publish --access=public passed prepublish/package gates and reached npm, then failed only with EOTP requiring a human OTP
Fix options:
- Add a valid
NPM_TOKEN repository secret with publish rights, or
- Configure npm trusted publishing/OIDC for this package and update the workflow accordingly.
After fixing auth, re-run publish for the current v1.1.0 release/tag or publish locally with OTP.
The v1.1.0 release workflow reached
npm publishon commit 066597f after package gates passed, but failed withENEEDAUTHbecauseNODE_AUTH_TOKENwas empty.Evidence:
.github/workflows/publish.ymluses${{ secrets.NPM_TOKEN }}NODE_AUTH_TOKEN:emptynpm publish --access=publicpassed prepublish/package gates and reached npm, then failed only withEOTPrequiring a human OTPFix options:
NPM_TOKENrepository secret with publish rights, orAfter fixing auth, re-run publish for the current v1.1.0 release/tag or publish locally with OTP.