chore: bump dependents to @metamask/utils@^12.0.0 - #10192
Merged
Conversation
4 tasks
cryptodev-2s
added this pull request to stack #10193
September 11, 2026 10:55
cryptodev-2s
force-pushed
the
chore/utils-bump-dependents
branch
from
September 11, 2026 11:03
f275644 to
a439c10
Compare
cryptodev-2s
marked this pull request as ready for review
September 11, 2026 11:04
cryptodev-2s
force-pushed
the
chore/utils-bump-dependents
branch
from
September 11, 2026 11:12
a439c10 to
4b34e4d
Compare
cryptodev-2s
force-pushed
the
chore/utils-bump-dependents
branch
from
September 11, 2026 11:20
4b34e4d to
9ecc84e
Compare
cryptodev-2s
force-pushed
the
chore/utils-bump-dependents
branch
from
September 11, 2026 12:37
9ecc84e to
e69079c
Compare
cryptodev-2s
force-pushed
the
chore/utils-bump-dependents
branch
3 times, most recently
from
September 11, 2026 13:12
d20c121 to
0f22715
Compare
github-merge-queue
Bot
removed this pull request from the merge queue because a pull request earlier in the stack was removed
Sep 11, 2026
cryptodev-2s
force-pushed
the
chore/utils-bump-dependents
branch
from
September 11, 2026 13:53
0f22715 to
e2129eb
Compare
mcmire
approved these changes
Sep 11, 2026
cryptodev-2s
added a commit
to MetaMask/utils
that referenced
this pull request
Sep 11, 2026
Step D-3 of the [package migration process](https://github.com/MetaMask/core/blob/main/docs/processes/package-migration-process-guide.md). `@metamask/utils` now lives in the core monorepo ([MetaMask/core#10185](MetaMask/core#10185) moved it, [MetaMask/core#10192](MetaMask/core#10192) bumped the dependents), so this swaps the "migration in progress" notice for the archived one from the guide. Open issues have been transferred to core and the remaining open PRs are commented and locked. Archiving the repo is the next step. <!-- CURSOR_SUMMARY --> --- > [!NOTE] > **Low Risk** > Documentation-only README change with no runtime or dependency impact. > > **Overview** > Updates the **README** migration banner for package migration step D-3: it no longer warns that migration is in progress or asks contributors to reopen PRs in **core**, and instead states that **`@metamask/utils`** has moved to the [**MetaMask/core**](https://github.com/MetaMask/core) monorepo, **this repo is archived**, and all future work should happen in **core**. > > The notice is also reformatted from a single-line HTML table into a multi-line layout; installation and API content are unchanged. > > <sup>Reviewed by [Cursor Bugbot](https://cursor.com/bugbot) for commit 13e0cdd. Bugbot is set up for automated code reviews on this repo. Configure [here](https://www.cursor.com/dashboard/bugbot).</sup> <!-- /CURSOR_SUMMARY -->
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.
Explanation
Follow up to #10185, which moved
@metamask/utilsintopackages/. This bumps its dependents to the local version.@metamask/utilsbumped from^11.12.0to^12.0.0in 79 packages and the root@metamask/utilsentry fromALLOWED_INCONSISTENT_DEPENDENCIESinyarn.config.cjs, which chore: integrate@metamask/utilsintopackages/#10185 added so that constraints would pass while the dependents were still on the published versionThese two PRs are meant to land together, so the intermediate state where dependents still resolve the published copy never reaches
main.Splitting it this way keeps #10185 reviewable: the move, the config rewiring and the type test change are separate from 79 mechanical version bumps.
References
@metamask/utilsintopackages/#10185Checklist
Note
Medium Risk
A major-version bump of a shared utility touches most packages; runtime risk is low if v12 is compatible, but consumers and lingering v11 transitive deps (keyring) can cause type or duplicate-package issues until fully aligned.
Overview
This PR aligns the monorepo with the in-repo
@metamask/utilsv12 after it was moved intopackages/(follow-up to #10185). 79 packages plus the root bump the dependency from^11.12.0to^12.0.0, with matching Unreleased changelog entries and an updated README dependency graph.Tooling is cleaned up so builds use the workspace package instead of the published copy:
tsconfig.packages.jsonnow maps@metamask/utilsto local source (the temporarynode_modulesoverride is removed), andyarn.config.cjsdrops theALLOWED_INCONSISTENT_DEPENDENCIESexception for@metamask/utils.There are small TypeScript follow-ups from the version split:
network-controllerremoves a stale@ts-expect-erroron Infura middleware now that types match v12, whilekeyring-controlleradds a documented@ts-expect-errorwhen casting legacy keyrings until@metamask/keyring-utilsalso depends on v12.Reviewed by Cursor Bugbot for commit 8bd8970. Bugbot is set up for automated code reviews on this repo. Configure here.