ci: Upgrade Yarn to 4.16.0 and update action-npm-publish to v6 - #203
Merged
Conversation
Mrtenz
marked this pull request as ready for review
June 8, 2026 12:24
cryptodev-2s
approved these changes
Jun 8, 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.
Summary
.yarnrc.ymlto match the module templateaction-npm-publishfrom v5 to v6 in the publish workflowid-token: writepermission and makesNPM_TOKENoptionalNote
Medium Risk
Changes how packages authenticate to npm during release; misconfiguration could block publishes or weaken the intended OIDC-only flow after bootstrap.
Overview
Updates release publishing CI to
MetaMask/action-npm-publish@v6, aligning dry-run and real publish jobs with the new action behavior.The
publish-releasecaller andpublish-npmjob now grantid-token: writefor OIDC-based npm auth.NPM_TOKENis optional at the workflow-call boundary (was required), with comments that the environment secret is only needed for the first publish and can be removed afterward. Workflow defaults addcontents: read; the dry-run step no longer relies on omitting a token via v5-specific behavior.Reviewed by Cursor Bugbot for commit 5fe131e. Bugbot is set up for automated code reviews on this repo. Configure here.