feat: OIDC npm support #19
Merged
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.
[FEATURE] Enable npm Trusted Publishing (OIDC)
Description
This PR enables npm Trusted Publishing (OIDC) for secure, token-free package publishing. By using OpenID Connect, we eliminate the need for long-lived NPM tokens in our secrets, improving security and enabling automatic provenance attestations for our packages.
Changes Made
id-token: writepermission to the release job (required for OIDC).pnpm/action-setupto v4 (using pnpm v10).actions/setup-nodeusage.actions/checkoutusage.publishConfigwithprovenance: trueandaccess: publicto enable build attestations and verified publising.Definition of Done
Before submitting this pull request, please ensure that the following criteria have been met:
Additional Notes
Important: This setup requires a one-time configuration on npmjs.com to add the GitHub repository as a trusted publisher. Once configured, the existing
NPM_TOKENcan eventually be removed, though it has been retained in the workflow for now as a fallback or parallel option during the transition.