ci: switch npm publish to OIDC trusted publishing - #110
Merged
Conversation
NPM_TOKEN secret was long-lived and required manual rotation. npm trusted publishing lets GitHub Actions authenticate via short-lived OIDC tokens and attaches provenance automatically, so the workflow no longer needs a stored secret.
npm audit flagged GHSA-rgw5-rvv9-x895 on the transitive brace-expansion dep, failing the Dependency audit CI job.
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.
Summary
NPM_TOKENsecret with npm's OIDC trusted publishingChanges
.github/workflows/npm-publish.yml: addid-token: writepermission, dropNODE_AUTH_TOKENenv, publish with--provenanceTest plan
@mulham28/pkgmap→ repomulhamna/pkgmap, workflownpm-publish.ymlmaintriggers publish successfully withoutNPM_TOKENNPM_TOKENsecret removed from repo settings after first successful OIDC publish