fix(ci): publish to npm via OIDC trusted publishing#203
Merged
Conversation
The elevated npm token (NPM_TOKEN_ELEVATED) can no longer be used, so the release job's npm authentication is broken. Switch to npm Trusted Publishing (OIDC), the same mechanism used by vercel/flags and vercel/front — without adopting changesets. - grant `id-token: write` on the release job so the runner can mint an OIDC token (the job previously had no permissions block, inheriting the default that blocks ID-token issuance) - drop `NODE_AUTH_TOKEN` from both publish steps; pnpm@11.1.3 performs the OIDC token exchange natively (native publish landed in 11.0.7, and 11.1.3 fixes the 404 when OIDC meets the actions/setup-node `.npmrc` placeholder) - enable `NPM_CONFIG_PROVENANCE` for signed provenance attestations Requires a Trusted Publisher to be configured on npm for @vercel/analytics (repo vercel/analytics, workflow release.yml). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
dferber90
reviewed
Jun 19, 2026
Per review feedback, move provenance out of the workflow env and into the package's publishConfig so it always applies, regardless of how publish is invoked. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
tobiaslins
approved these changes
Jun 19, 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
3 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.
Why
The release job authenticated to npm with
NPM_TOKEN_ELEVATED. That elevated token can no longer be used (permissions revoked), so publishing is broken.This switches publishing to npm Trusted Publishing (OIDC) — the same mechanism
vercel/flags— without adopting changesets. The workflow keeps its existing trigger (release: [published]) and its beta/stable split.🤖 Generated with Claude Code