ci: public npm publish via NPM_TOKEN (n8n-public pattern) - #9
Closed
vigubikReply wants to merge 1 commit into
Closed
ci: public npm publish via NPM_TOKEN (n8n-public pattern)#9vigubikReply wants to merge 1 commit into
vigubikReply wants to merge 1 commit into
Conversation
OIDC trusted publishing kept failing at the token exchange (npmjs 'package not found' for reply-cli). Switch to a scoped automation token via NODE_AUTH_TOKEN, matching reply-team/n8n-public. Approval gate kept. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Contributor
Author
|
OIDC trusted publishing works after fixing the npmjs Trusted Publisher repo-name typo (repy-cli -> reply-cli). reply-cli@0.3.0 published via OIDC with provenance. Keeping the tokenless OIDC path; closing this token fallback. |
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
1 participant
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.
Switches the public-npm release from OIDC trusted publishing to a scoped automation token, matching
reply-team/n8n-public.Why: OIDC was fully working on our side (id-token fetched with the right audience, exchange POSTed), but npmjs rejected the exchange with
OIDC token exchange error - package not found— the trusted-publisher config on thereply-clipackage (owned byreply-io) isn't matching our claims. That's an npmjs-side config issue we can't resolve from CI, so per decision we use token auth.Change:
npm publishnow runs withNODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}(setup-node'sregistry-url.npmrcuses it). Provenance and thenpm-publicapproval gate are kept.Required before dispatch: add an environment secret
NPM_TOKENon thenpm-publicenvironment — a token that can publishreply-cli(see PR discussion / release runbook).Ref: REPLY-51236