Prepare NPM trusted publishing #2792
Merged
Conversation
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
This PR adjusts the GHA we use to publish the npmjs packages for NPM Trusted publishing. Please do not set to automeerge. I will merge once I finished the setup fpr all packages on npm. Note: For the future we need to publish new packages once manually in order to configure them for trusted publishing.
Contributor
There was a problem hiding this comment.
Pull request overview
This PR configures the GitHub Actions workflow to use NPM trusted publishing, which uses OpenID Connect (OIDC) authentication instead of manual NPM tokens. The changes add the required OIDC permission, remove the legacy token-based authentication, and upgrade npm to ensure compatibility with trusted publishing features.
Key Changes:
- Adds
id-token: writepermission for OIDC authentication - Removes manual NPM_TOKEN authentication and
npm whoamiverification - Upgrades npm to the latest version before publishing
Comments suppressed due to low confidence (1)
.github/workflows/release-npm.yml:129
- When using NPM trusted publishing with OIDC, the
--provenanceflag should be added tonpm publishcommands to generate provenance attestations. This provides transparency about where and how the package was built.
Add --provenance to both publish commands:
npm publish --workspaces --tag dev --provenanceand
npm publish --workspaces --provenanceReference: https://docs.npmjs.com/generating-provenance-statements
npm publish --workspaces --tag dev
else
npm publish --workspaces
lauckhart
approved these changes
Dec 6, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR adjusts the GHA we use to publish the npmjs packages for NPM Trusted publishing.
Please do not set to automerge. I will merge once I finished the setup for all packages on npm.
Note: For the future we need to publish new packages once manually in order to configure them for trusted publishing.
Docs: https://docs.npmjs.com/trusted-publishers/#configuring-trusted-publishing