ci: add npm provenance attestation to release publish#18
Merged
Conversation
drewstone
added a commit
that referenced
this pull request
Jun 2, 2026
Supersedes #18's provenance-on-token-path: pnpm signs provenance but doesn't mint the OIDC credential, and the NPM_TOKEN is dead. npm install -g npm@latest + npm publish --provenance, drop NPM_TOKEN + setup-node registry-url. No workspace deps so npm publish is safe. Needs the npmjs Trusted Publisher (org tangle-network, repo agent-knowledge, workflow publish.yml) configured once.
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.
Problem
Releases publish to npm with a token but no provenance attestation — the published versions carry no SLSA provenance, so consumers can't verify the build origin.
Change
Add
--provenanceto thepnpm publishcommand. The job already grantsid-token: writeand the repo is public, so this attaches a signed provenance attestation using the existing token auth — non-breaking, no secret changes.Notes
NPM_TOKENto rotate) is a separate step: register a Trusted Publisher on npmjs.com for this package → repo +publish.yml. The workflow is already OIDC-capable (id-token: write).