ci: use npm OIDC trusted publishing for releases#390
Merged
Conversation
Replaces the long-lived NPM_AUTH_TOKEN with npm's OIDC trusted publishing. Adds id-token: write permission, upgrades npm to a version that supports trusted publishing (>= 11.5.1), and drops the npm token env vars. Lerna v9+ handles the OIDC exchange automatically.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
What
Switches the release workflow from a long-lived npm token to npm's OIDC trusted publishing.
id-token: writepermission (the OIDC token npm verifies)NODE_AUTH_TOKEN/NPM_TOKENenv varslatestin CI — trusted publishing needs npm ≥ 11.5.1, but Node 22 ships npm 10.xLerna is already
^9.0.7, and v9+ performs the OIDC exchange automatically, so thelerna publishcommands are unchanged. This also emits provenance attestations for free.Required manual step before merging is useful
Trusted publishers are configured per package on npmjs.com. For each publishable package (
@revideo/core,@revideo/2d,@revideo/cli,@revideo/create,@revideo/ffmpeg,@revideo/player,@revideo/player-react,@revideo/renderer,@revideo/telemetry,@revideo/ui,@revideo/vite-plugin):npmjs.com → package → Settings → Trusted Publisher → GitHub Actions:
midrender/revideopublish.ymlThe
NPM_AUTH_TOKENsecret can be deleted after the first successful trusted-publish run.Notes
publish.ymlwill break publishing until every package's trusted-publisher config is updated.