ci: enable npm provenance attestations#159
Merged
Merged
Conversation
Sets NPM_CONFIG_PROVENANCE=true in the release workflow. The env var is reliable because multi-semantic-release runs npm publish from each package subdirectory, and npm only reads .npmrc from the cwd. Also verify: the npm token is granular (not classic) scoped to @idempot-dev. Classic tokens are being deprecated.
Deploying idempot-js with
|
| Latest commit: |
35b10ca
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://219c1607.idempot-js.pages.dev |
| Branch Preview URL: | https://feat-npm-provenance.idempot-js.pages.dev |
mroderick
marked this pull request as ready for review
June 13, 2026 09:37
This was referenced Jun 13, 2026
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.
Enables npm provenance attestations via NPM_CONFIG_PROVENANCE in the release workflow.