Repository navigation
ci(publish): publish to npm with trusted publishing - #30
Merged
Merged
Conversation
The publish job now authenticates to npm with the workflow's own OIDC identity instead of a stored npm token, which had expired and failed the v1.4.0 publish. Trusted publishing needs npm 11.5.1 or later, so the job upgrades npm before publishing. Provenance is unchanged. Co-Authored-By: Claude Opus 5.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.
What
The npm publish job authenticates with GitHub Actions OIDC (npm trusted publishing) instead of the
TANGO_NPM_TOKENsecret, and upgrades npm to 11 first, since trusted publishing needs npm 11.5.1 or later.Why
The stored token had expired, so publishing v1.4.0 failed with
E404 Not Found - PUT https://registry.npmjs.org/@makegov%2ftango-node, npm's response to a token that can't publish. A trusted publisher has no secret to expire or rotate. The job already hadid-token: writefor provenance.Before merge / after
publish.ymlmust be configured on the package at npmjs.com.TANGO_NPM_TOKENcan then be deleted.[skip changelog]
🤖 Generated with Claude Code