Repository navigation
chore: migrate npm publishing to trusted publishing - #46
Merged
Merged
Conversation
Mrtenz
reviewed
Jun 11, 2026
| @@ -1,2 +1,2 @@ | |||
| name: Publish Release | |||
|
|
|||
Member
There was a problem hiding this comment.
This needs top-level permissions:
permissions:
contents: read
Mrtenz
approved these changes
Jun 11, 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
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.
Description
Migrates NPM publishing to trusted publishing support via
MetaMask/action-npm-publish@v6.Changes:
MetaMask/action-npm-publish@v6.id-token: writepermission for OIDC-based publishing.NPM_TOKENoptional in the reusable publish workflow.packageManagertoyarn@4.16.0and regeneratesyarn.lock.Testing
git diff --check.Note
Medium Risk
Changes the production npm publish path and auth model (OIDC vs long-lived token); misconfiguration could block releases or require one-time NPM_TOKEN setup.
Overview
Switches release publishing to npm trusted publishing by upgrading
MetaMask/action-npm-publishfrom v5 to v6 and enabling OIDC (id-token: writeon the caller andpublish-npmjob).The reusable publish workflow now treats
NPM_TOKENas optional (only for an initial publish per updated comments); the dry-run step no longer relies on omitting a token comment-wise—it uses the same v6 action. Workflow-levelcontents: readis added, andpackageManageris bumped to yarn@4.16.0 with a regeneratedyarn.lock.Reviewed by Cursor Bugbot for commit 84f4560. Bugbot is set up for automated code reviews on this repo. Configure here.