Add npm trusted publishing support #38
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
- Add id-token, contents, and pull-requests write permissions to release job - Add npm update step to ensure latest npm version for provenance support - Add --provenance flag for npm publish - Add changeset for all packages - Enables automated publishing via OIDC without requiring OTP
jgoz
commented
Oct 21, 2025
Merged
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 adds support for npm trusted publishing via OIDC, which allows automated publishing without requiring OTP tokens.
Changes
id-token: write,contents: write, andpull-requests: writepermissions to the release job--provenanceflag in the npm publish commandBenefits
References
Next Steps
After merging this PR, you'll need to configure the trusted publisher on npm for each package:
For each package: