Repository navigation
fix: add NODE_AUTH_TOKEN for npm publish authentication - #32
Merged
Merged
Conversation
Trusted Publisher OIDC alone resulted in 404 on npm PUT. Adding NODE_AUTH_TOKEN as env var for the publish step. Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
问题
Release workflow 在 publish 步骤报 404:
虽然 OIDC provenance 签名成功,但 Trusted Publisher 的认证没有传递到 npm publish,导致
PUT请求被拒。修复
在 Publish to npm 步骤中添加
NODE_AUTH_TOKEN环境变量:setup-node@v4配置了registry-url后会自动写入.npmrc,通过NODE_AUTH_TOKEN完成认证。前置条件
需要确保 GitHub Secrets 中已配置
NPM_TOKEN(npm access token,类型为 Automation 或 Publish)。