ci: publish to npm via OIDC trusted publishing - #4
Merged
Conversation
Drop the dead NPM_TOKEN secret and publish via npm Trusted Publishing (OIDC). pnpm 10 exchanges the workflow's id-token (id-token: write is already granted) for a short-lived publish credential and attaches provenance automatically — no long-lived token to expire. Requires a Trusted Publisher configured for ink-uplot on npmjs.com pointing at this repo + publish.yml.
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.
Fixes the broken publish workflow (every run since March has failed with
E404— theNPM_TOKENsecret is invalid/expired, so npm has been stuck at 0.1.4 while the git version climbed to 0.2.2).Switches to npm Trusted Publishing (OIDC): removes
NODE_AUTH_TOKEN; pnpm 10 exchanges the workflow's OIDCid-tokenfor a short-lived publish credential and attaches provenance automatically. No long-lived token to rotate.Merge only after the Trusted Publisher is configured for
ink-uploton npmjs.com (GitHub Actions → repoplanadecu/ink-uplot→ workflowpublish.yml). Merging triggers the workflow, which will publish the next patch version via OIDC.