ci: authenticate npm publish with the org token#5
Merged
Conversation
No trusted publisher is configured on npmjs for this package, so the OIDC-only publish 404s. Use NPM_AUTH_TOKEN via NODE_AUTH_TOKEN (setup-node registry-url wires .npmrc to it); provenance is still attested through the OIDC id-token. Co-Authored-By: Claude Opus 4.8 (1M context) <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
2 participants
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.
Summary
The release pipeline's npm publish fails with E404 on PUT because it relies on OIDC trusted publishing, which is not configured on npmjs for this package (the Rokt kit has it; ours does not). Wire
NPM_AUTH_TOKENinto the release job asNODE_AUTH_TOKENso setup-node's registry-url .npmrc picks it up. Provenance is still attested via the OIDC id-token.Testing Plan
Next release run (the 1.1.0 attempt) validates this end to end.