chore: switch npm releases to trusted publishing (OIDC)#585
Merged
Conversation
Remove long-lived NPM_TOKEN from CI and rely on GitHub Actions OIDC. Run semantic-release on Node 22 to meet npm trusted publishing requirements. Co-authored-by: Cursor <cursoragent@cursor.com>
jeffsee55
requested review from
a team,
icyJoseph,
ijjk and
styfle
as code owners
styfle
reviewed
May 22, 2026
styfle
approved these changes
May 22, 2026
Member
styfle
left a comment
styfle
left a comment
There was a problem hiding this comment.
Looks good but I don't have access to the link in your PR description to set this up
Member
|
@jeffsee55 Its failing with no token specified https://github.com/vercel/nft/actions/runs/26301501589/job/77427550877#step:12:57 |
Contributor
Author
|
@styfle I think this is the expected error until trusted publishing is enabled |
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
@vercel/nftfrom CI using npm trusted publishing (GitHub Actions OIDC) instead of the long-livedNPM_TOKEN_ELEVATEDsecret.repository.urlinpackage.jsonso npm can verify the GitHub repo during OIDC publish.Prerequisites (before merge / first release)
Configure a trusted publisher on npm for
@vercel/nft:vercel/nftci.ymlAfter the first successful OIDC publish, consider restricting package publishing access to disallow tokens.
Test plan
ci.ymlmainand confirm semantic-release publishes withoutNPM_TOKENMade with Cursor