Open
Conversation
- Add OIDC permissions (id-token: write, contents: read) for trusted publishing - Replace NODE_AUTH_TOKEN with npx npm@latest publish --provenance
hillna
force-pushed
the
nick/inf-65-update-npm-publish-workflows-to-use-trusted-publishing
branch
2 times, most recently
from
73b732a to
d3c6baa
Compare
- Upgrade to Yarn 4.12.0 for OIDC support (PR yarnpkg/berry#6898) - Replace npx npm@latest publish --provenance with yarn npm publish - Provenance is automatic with OIDC trusted publishing - Add packageManager field where missing
hillna
force-pushed
the
nick/inf-65-update-npm-publish-workflows-to-use-trusted-publishing
branch
from
d3c6baa to
3629163
Compare
Switch from yarn pack + npx npm publish to yarn npm publish for OIDC trusted publishing support.
jtbandes
approved these changes
Jan 29, 2026
.github/workflows/ci.yml
Outdated
| - uses: actions/checkout@v6 | ||
| - uses: actions/setup-node@v6 | ||
| with: | ||
| node-version: 16.x |
jtbandes
reviewed
Jan 29, 2026
Member
jtbandes
left a comment
jtbandes
left a comment
There was a problem hiding this comment.
Actually I'm not sure this will work since the yarn version is too old in this repo.
Yarn 4.10.0+ adds OIDC authentication support for GitHub Actions and GitLab CI, enabling npm trusted publishing without long-lived tokens. Co-authored-by: Cursor <cursoragent@cursor.com>
Corepack must be enabled for the packageManager field to work properly. Also updates from EOL Node.js 16 to Node.js 22. Co-authored-by: Cursor <cursoragent@cursor.com>
The setup-node action with cache: yarn runs yarn to find the cache directory during its own execution, so corepack must be enabled first. Co-authored-by: Cursor <cursoragent@cursor.com>
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
Update npm publish workflow to use OIDC trusted publishing with provenance.
Changes
id-token: writeandcontents: readpermissions for OIDC authenticationyarn npm publishwith--provenanceflag for supply chain securityNODE_AUTH_TOKENsecret (no longer needed with OIDC)Status
✅ Trusted publishing has been configured on npmjs.com for this package.