Use npm trusted publishing (OIDC) for package releases#586
Merged
Conversation
carlostxm
force-pushed
the
chore/npm-trusted-publishing
branch
3 times, most recently
from
a4ecb69 to
1141e4a
Compare
Removes dependency on long-lived npm tokens that expire every 90 days. Co-authored-by: Cursor <cursoragent@cursor.com>
carlostxm
force-pushed
the
chore/npm-trusted-publishing
branch
from
1141e4a to
0274c2a
Compare
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
2 participants
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 OIDC trusted publishing for npmid-token: writepermission to enable provenance attestation--provenanceflag for supply chain securitySetup done
Trusted publisher configured on npmjs.com for this repo/workflow (no environment).
Test plan