Repository navigation
Use isolated npm trusted publishing for releases - #357
Merged
Merged
Conversation
naqvitalha
approved these changes
Sep 25, 2026
michaelrhughes
marked this pull request as ready for review
September 25, 2026 17:35
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
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.
Replace
NPM_TOKENauthentication with npm trusted publishing. A read-only job builds and packs the release; a separate job has OIDC permission and publishes the tarball without installing dependencies or executing lifecycle scripts. Release dispatches must target a tag. Actions, runner versions, and the OIDC-capable Node version are pinned, and checkout credentials are not persisted.The npm trusted publisher is configured. The publish step explicitly sets
NPM_TOKENandNODE_AUTH_TOKENto empty strings. The first end-to-end OIDC release still needs verification; no package has been published as part of this change. After verification, confirm other token consumers before revoking the old credential and removing the Actions secret. CONTRIBUTING.md documents the release and cleanup steps.