feat: migrate npm publish to OIDC trusted publishing#16
Merged
Conversation
- Add id-token: write permission for OIDC token generation - Upgrade publish job to Node 24 + actions/checkout@v6 + actions/setup-node@v6 (npm OIDC requires npm 11.5.1+ / Node 22.14+) - Remove NODE_AUTH_TOKEN (npm CLI auto-detects OIDC in CI) - Add --provenance flag to npm publish command - Add provenance: true to publishConfig in package.json Made-with: Cursor
…into feat/npm-oidc-publish
hasithaishere
approved these changes
Apr 23, 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
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.
Uh oh!
There was an error while loading. Please reload this page.