Release 1094.0.0 by FrederikBolding · Pull Request #9392 · MetaMask/core

FrederikBolding · 2026-07-06T12:58:29Z

Explanation

Release PR for a breaking change to messenger.

Note

Medium Risk
A semver-major bump to the shared messenger library touches most controllers and services; the breaking CLI removal can break release/tooling scripts until clients switch to @metamask/messenger-cli.

Overview
Monorepo release 1094.0.0 rolls out @metamask/messenger 2.0.0 across the workspace: root and dependent packages move from ^1.2.0 to ^2.0.0, with matching Unreleased changelog lines (#9392).

The messenger package is versioned 2.0.0 in this release (changelog section promoted from Unreleased). That major includes breaking removal of the in-package generate-action-types CLI in favor of @metamask/messenger-cli (messenger-action-types), plus additions like getRegisteredActionTypes and buildChild (already documented under the 2.0.0 heading).

Consumers upgrading the monorepo or individual @metamask/* packages must align on messenger 2.x and update any scripts still invoking the old CLI.

^{Reviewed by Cursor Bugbot for commit 41a142d. Bugbot is set up for automated code reviews on this repo. Configure here.}

metamask-ci · 2026-07-06T13:00:54Z

✅ Changelogs updated and pushed.

)  ## **Description** Bumps `@metamask/assets-controller` from the patched `10.0.1` to `^10.1.0` ([changelog](https://github.com/MetaMask/core/blob/main/packages/assets-controller/CHANGELOG.md#1010)). Notable changes in `10.1.0`: - **Fixed**: Fetch balances when switching account groups, enabling RPC-only networks, or after a new account is added to the account tree ([core#9388](MetaMask/core#9388)). This release contains the exact fix that was previously applied via the local yarn patch (`@metamask-assets-controller-npm-10.0.1-d3c86d8983.patch`), so this PR stops using the patch in `package.json` resolutions/dependencies. The patch file itself is intentionally left in `.yarn/patches/` (removing it would require an additional codeowner review); it is no longer referenced by the install. - **Added**: temporary `tempMigrateAssetsInfoMetadataAssets3346` constructor option ([core#9393](MetaMask/core#9393)). Wiring this option up is intentionally **not** done here and will be a fast-follow in a separate PR. - **Changed**: `@metamask/messenger` bumped from `^1.2.0` to `^2.0.0` ([core#9392](MetaMask/core#9392)). No action needed here anymore: `main` has since migrated the app to messenger v2, so after merging `main` into this branch everything dedupes onto a single `@metamask/messenger@2.0.0` copy. Also updates the `@metamask/assets-controller@npm:^9.1.0` resolution (needed for `@metamask/transaction-pay-controller`'s transitive request) to point at `^10.1.0` instead of the patch. The previous `@npm:^10.0.1` resolution entry is removed because `^10.0.1` now naturally resolves to `10.1.0`. `yarn lavamoat:auto`, `yarn allow-scripts auto`, and `yarn lint:lockfile:dedupe:fix` were run — no policy or allow-scripts changes were produced. `yarn attributions:generate` produced only unrelated stale-file churn, so attribution updates are left to `@metamaskbot update-attributions` if required. ## **Changelog** CHANGELOG entry: null ## **Related issues** Related to: MetaMask/core#9388, MetaMask/core#9392 ## **Manual testing steps** 1. Run the extension and unlock the wallet. 2. Go to the homepage asset list. 3. Add a new account to an account group and switch account groups. 4. Verify balances populate for the new account, including on custom/RPC-only networks. 5. Enable an RPC-only network (e.g. a custom chain) and verify token balances are fetched.  ## **Pre-merge author checklist** - [x] I've followed [MetaMask Contributor Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask Extension Coding Standards](https://github.com/MetaMask/metamask-extension/blob/main/.github/guidelines/CODING_GUIDELINES.md). - [x] I've completed the PR template to the best of my ability - [ ] I’ve included tests if applicable - [ ] I’ve documented my code using [JSDoc](https://jsdoc.app/) format if applicable - [ ] I’ve applied the right labels on the PR (see [labeling guidelines](https://github.com/MetaMask/metamask-extension/blob/main/.github/guidelines/LABELING_GUIDELINES.md)). Not required for external contributors. ## **Pre-merge reviewer checklist** - [ ] I've manually tested the PR (e.g. pull and build branch, run the app, test code being changed). - [ ] I confirm that this PR addresses all acceptance criteria described in the ticket it closes and includes the necessary testing evidence such as recordings and or screenshots.  <div><a href="https://cursor.com/agents/bc-e5245e2b-5547-4357-8a2c-94466489dd60"><picture><source media="(prefers-color-scheme: dark)" srcset="https://cursor.com/assets/images/open-in-web-dark.png"><source media="(prefers-color-scheme: light)" srcset="https://cursor.com/assets/images/open-in-web-light.png"><img alt="Open in Web" width="114" height="28" src="https://cursor.com/assets/images/open-in-web-dark.png"></picture></a> <a href="https://cursor.com/background-agent?bcId=bc-e5245e2b-5547-4357-8a2c-94466489dd60"><picture><source media="(prefers-color-scheme: dark)" srcset="https://cursor.com/assets/images/open-in-cursor-dark.png"><source media="(prefers-color-scheme: light)" srcset="https://cursor.com/assets/images/open-in-cursor-light.png"><img alt="Open in Cursor" width="131" height="28" src="https://cursor.com/assets/images/open-in-cursor-dark.png"></picture></a> </div>

## **Description** Bumps `@metamask/assets-controller` from the patched `10.0.1` to `^10.1.0` ([changelog](https://github.com/MetaMask/core/blob/main/packages/assets-controller/CHANGELOG.md#1010)). Notable changes in `10.1.0`: - **Fixed**: Fetch balances when switching account groups, enabling RPC-only networks, or after a new account is added to the account tree ([core#9388](MetaMask/core#9388)). This release contains the exact fix that was previously applied via the local yarn patch (`@metamask-assets-controller-npm-10.0.1-d3c86d8983.patch`), so this PR stops using the patch in `package.json` resolutions/dependencies. The patch file itself is intentionally left in `.yarn/patches/` (removing it would require an additional codeowner review); it is no longer referenced by the install. - **Added**: temporary `tempMigrateAssetsInfoMetadataAssets3346` constructor option ([core#9393](MetaMask/core#9393)). Wiring this option up is intentionally **not** done here and will be a fast-follow in a separate PR. - **Changed**: `@metamask/messenger` bumped from `^1.2.0` to `^2.0.0` ([core#9392](MetaMask/core#9392)). No change needed here: the existing blanket `"@metamask/messenger": "^1.2.0"` resolution keeps a single deduped messenger copy (`1.2.0`) for the whole app. `@metamask/assets-controller@10.1.0` does not use any messenger v2-only APIs (`buildChild`, `getRegisteredActionTypes`), so this is safe at runtime. Validated with `yarn setup:expo`, `yarn lint:tsc` (zero errors), and the assets-controller unit tests (`assets-controller-init.test.ts`, `assets-controller.test.ts` — 30 passed). ## **Changelog** CHANGELOG entry: null ## **Related issues** Refs: MetaMask/core#9388 ## **Manual testing steps** ```gherkin Feature: unified assets balances (AssetsController) Scenario: user adds a new account to the account tree Given the wallet is unlocked with an existing account group When user creates or imports a new account Then balances for the new account are fetched and displayed, including on custom/RPC-only networks Scenario: user enables an RPC-only network Given the wallet is unlocked When user enables a custom RPC network Then token balances on that network are fetched without requiring an app restart ``` ## **Screenshots/Recordings** N/A — dependency bump only, no UI changes. ### **Before**  ### **After**  ## **Pre-merge author checklist** - [x] I've followed [MetaMask Contributor Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask Mobile Coding Standards](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/CODING_GUIDELINES.md). - [x] I've completed the PR template to the best of my ability - [x] I've included tests if applicable - [x] I've documented my code using [JSDoc](https://jsdoc.app/) format if applicable - [ ] I've applied the right labels on the PR (see [labeling guidelines](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/LABELING_GUIDELINES.md)). Not required for external contributors. #### Performance checks (if applicable) - [ ] I've tested on Android - Ideally on a mid-range device; emulator is acceptable - [ ] I've tested with a power user scenario - Use these [power-user SRPs](https://consensyssoftware.atlassian.net/wiki/spaces/TL1/pages/edit-v2/401401446401?draftShareId=9d77e1e1-4bdc-4be1-9ebb-ccd916988d93) to import wallets with many accounts and tokens - [ ] I've instrumented key operations with Sentry traces for production performance metrics - See [`trace()`](/app/util/trace.ts) for usage and [`addToken`](/app/components/Views/AddAsset/components/AddCustomToken/AddCustomToken.tsx#L274) for an example For performance guidelines and tooling, see the [Performance Guide](https://consensyssoftware.atlassian.net/wiki/spaces/TL1/pages/400085549067/Performance+Guide+for+Engineers). ## **Pre-merge reviewer checklist** - [ ] I've manually tested the PR (e.g. pull and build branch, run the app, test code being changed). - [ ] I confirm that this PR addresses all acceptance criteria described in the ticket it closes and includes the necessary testing evidence such as recordings and or screenshots.  <div><a href="https://cursor.com/agents/bc-e5245e2b-5547-4357-8a2c-94466489dd60"><picture><source media="(prefers-color-scheme: dark)" srcset="https://cursor.com/assets/images/open-in-web-dark.png"><source media="(prefers-color-scheme: light)" srcset="https://cursor.com/assets/images/open-in-web-light.png"><img alt="Open in Web" width="114" height="28" src="https://cursor.com/assets/images/open-in-web-dark.png"></picture></a> <a href="https://cursor.com/background-agent?bcId=bc-e5245e2b-5547-4357-8a2c-94466489dd60"><picture><source media="(prefers-color-scheme: dark)" srcset="https://cursor.com/assets/images/open-in-cursor-dark.png"><source media="(prefers-color-scheme: light)" srcset="https://cursor.com/assets/images/open-in-cursor-light.png"><img alt="Open in Cursor" width="131" height="28" src="https://cursor.com/assets/images/open-in-cursor-dark.png"></picture></a> </div>

…er` (MetaMask#44766)  ## **Description**  ~~Using preview build from MetaMask/core#9611 Bumping `@metamask/network-enablement-controller` to `^6.0.0` ```markdown ## [6.0.0] ### Added - Expose missing public `NetworkEnablementController` method through its messenger ([MetaMask#9660](MetaMask/core#9660)) - The following action is now available: - `NetworkEnablementController:restoreEnabledNetworkMap` - Corresponding action type (`NetworkEnablementControllerRestoreEnabledNetworkMapAction`) is available as well. ### Changed - **BREAKING:** Popular-network classification is now augmented by `ConfigRegistryController` ([MetaMask#9611](MetaMask/core#9611)) - `NetworkEnablementControllerMessenger` now requires the `ConfigRegistryController:getState` action to be available. - Bump `@metamask/transaction-controller` from `^69.0.0` to `^69.3.0` ([MetaMask#9568](MetaMask/core#9568), [MetaMask#9589](MetaMask/core#9589), [MetaMask#9593](MetaMask/core#9593), [MetaMask#9693](MetaMask/core#9693)) - Bump `@metamask/keyring-api` from `^23.5.0` to `^23.7.0` ([MetaMask#9676](MetaMask/core#9676)) - Bump `@metamask/config-registry-controller` from `^0.4.1` to `^1.0.0` ([MetaMask#9706](MetaMask/core#9706)) ``` and `@metamask/config-registry-controller` to `^1.0.0` ```markdown ## [1.0.0] ### Added - Add `ConfigRegistryControllerStateChangedEvent` (`ConfigRegistryController:stateChanged`) to the controller's events ([MetaMask#9595](MetaMask/core#9595)) - Add `ConfigRegistryController.getNetworkConfigByCaip2ChainId` method to retrieve a network config by its CAIP-2 chain ID ([MetaMask#9597](MetaMask/core#9597), [MetaMask#9606](MetaMask/core#9606)) - The method returns the network config if found, or `undefined` if not found. - The method is also accessible via the controller's messenger as `ConfigRegistryController:getNetworkConfigByCaip2ChainId`. ### Changed - **BREAKING:** `ConfigRegistryControllerState.configs.networks` is now a `Record<Caip2ChainId, RegistryNetworkConfig>` instead of a `Record<string, RegistryNetworkConfig>` ([MetaMask#9606](MetaMask/core#9606)) - Bump `@metamask/utils` from `^11.9.0` to `^11.11.0` ([MetaMask#9074](MetaMask/core#9074)) - Bump `@metamask/controller-utils` from `^12.1.1` to `^12.3.0` ([MetaMask#9083](MetaMask/core#9083), [MetaMask#9218](MetaMask/core#9218)) - Bump `@metamask/profile-sync-controller` from `^28.1.1` to `^28.3.0` ([MetaMask#9119](MetaMask/core#9119), [MetaMask#9463](MetaMask/core#9463)) - Bump `@metamask/keyring-controller` from `^27.0.0` to `^27.1.0` ([MetaMask#9129](MetaMask/core#9129)) - Bump `@metamask/polling-controller` from `^16.0.6` to `^16.0.8` ([MetaMask#9218](MetaMask/core#9218), [MetaMask#9349](MetaMask/core#9349)) - Bump `@metamask/messenger` from `^1.2.0` to `^2.0.0` ([MetaMask#9392](MetaMask/core#9392)) ### Removed - **BREAKING:** Removed `ConfigRegistryControllerStateChangeEvent` type in favor of `ConfigRegistryControllerStateChangedEvent` ([MetaMask#9595](MetaMask/core#9595)) ``` ## **Changelog**  CHANGELOG entry: null ## **Related issues** Related: https://consensyssoftware.atlassian.net/browse/WPN-1710 ## **Manual testing steps** 1. Verify the network switching and asset polling work same as before ## **Screenshots/Recordings**  ### **Before**  ### **After**  ## **Pre-merge author checklist** - [ ] I've followed [MetaMask Contributor Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask Extension Coding Standards](https://github.com/MetaMask/metamask-extension/blob/main/.github/guidelines/CODING_GUIDELINES.md). - [ ] I've completed the PR template to the best of my ability - [ ] I’ve included tests if applicable - [ ] I’ve documented my code using [JSDoc](https://jsdoc.app/) format if applicable - [ ] I’ve applied the right labels on the PR (see [labeling guidelines](https://github.com/MetaMask/metamask-extension/blob/main/.github/guidelines/LABELING_GUIDELINES.md)). Not required for external contributors. ## **Pre-merge reviewer checklist** - [ ] I've manually tested the PR (e.g. pull and build branch, run the app, test code being changed). - [ ] I confirm that this PR addresses all acceptance criteria described in the ticket it closes and includes the necessary testing evidence such as recordings and or screenshots.  --- > [!NOTE] > **Medium Risk** > Popular-network behavior now depends on config registry state at runtime; incorrect messenger wiring would break network enablement, but the change is limited to dependency versions and one delegate action. > > **Overview** > Bumps **`@metamask/network-enablement-controller`** to `^6.0.0` and **`@metamask/config-registry-controller`** to `^1.0.0`, with lockfile updates. > > Wires **`NetworkEnablementController`** to the config registry by delegating **`ConfigRegistryController:getState`** on its messenger so v6 can use registry data for popular-network classification. > > Config-registry selector tests now build mock registry entries with the **`RegistryNetworkConfig`** type instead of untyped inline objects, matching the v1 typed `configs.networks` shape. > > <sup>Reviewed by [Cursor Bugbot](https://cursor.com/bugbot) for commit 1ddf8cd. Bugbot is set up for automated code reviews on this repo. Configure [here](https://www.cursor.com/dashboard/bugbot).</sup>  --------- Co-authored-by: MetaMask Bot <metamaskbot@users.noreply.github.com> Co-authored-by: Guillaume Roux <guillaumeroux123@gmail.com>

…er` (#44766)  ## **Description**  ~~Using preview build from MetaMask/core#9611 Bumping `@metamask/network-enablement-controller` to `^6.0.0` ```markdown ## [6.0.0] ### Added - Expose missing public `NetworkEnablementController` method through its messenger ([#9660](MetaMask/core#9660)) - The following action is now available: - `NetworkEnablementController:restoreEnabledNetworkMap` - Corresponding action type (`NetworkEnablementControllerRestoreEnabledNetworkMapAction`) is available as well. ### Changed - **BREAKING:** Popular-network classification is now augmented by `ConfigRegistryController` ([#9611](MetaMask/core#9611)) - `NetworkEnablementControllerMessenger` now requires the `ConfigRegistryController:getState` action to be available. - Bump `@metamask/transaction-controller` from `^69.0.0` to `^69.3.0` ([#9568](MetaMask/core#9568), [#9589](MetaMask/core#9589), [#9593](MetaMask/core#9593), [#9693](MetaMask/core#9693)) - Bump `@metamask/keyring-api` from `^23.5.0` to `^23.7.0` ([#9676](MetaMask/core#9676)) - Bump `@metamask/config-registry-controller` from `^0.4.1` to `^1.0.0` ([#9706](MetaMask/core#9706)) ``` and `@metamask/config-registry-controller` to `^1.0.0` ```markdown ## [1.0.0] ### Added - Add `ConfigRegistryControllerStateChangedEvent` (`ConfigRegistryController:stateChanged`) to the controller's events ([#9595](MetaMask/core#9595)) - Add `ConfigRegistryController.getNetworkConfigByCaip2ChainId` method to retrieve a network config by its CAIP-2 chain ID ([#9597](MetaMask/core#9597), [#9606](MetaMask/core#9606)) - The method returns the network config if found, or `undefined` if not found. - The method is also accessible via the controller's messenger as `ConfigRegistryController:getNetworkConfigByCaip2ChainId`. ### Changed - **BREAKING:** `ConfigRegistryControllerState.configs.networks` is now a `Record<Caip2ChainId, RegistryNetworkConfig>` instead of a `Record<string, RegistryNetworkConfig>` ([#9606](MetaMask/core#9606)) - Bump `@metamask/utils` from `^11.9.0` to `^11.11.0` ([#9074](MetaMask/core#9074)) - Bump `@metamask/controller-utils` from `^12.1.1` to `^12.3.0` ([#9083](MetaMask/core#9083), [#9218](MetaMask/core#9218)) - Bump `@metamask/profile-sync-controller` from `^28.1.1` to `^28.3.0` ([#9119](MetaMask/core#9119), [#9463](MetaMask/core#9463)) - Bump `@metamask/keyring-controller` from `^27.0.0` to `^27.1.0` ([#9129](MetaMask/core#9129)) - Bump `@metamask/polling-controller` from `^16.0.6` to `^16.0.8` ([#9218](MetaMask/core#9218), [#9349](MetaMask/core#9349)) - Bump `@metamask/messenger` from `^1.2.0` to `^2.0.0` ([#9392](MetaMask/core#9392)) ### Removed - **BREAKING:** Removed `ConfigRegistryControllerStateChangeEvent` type in favor of `ConfigRegistryControllerStateChangedEvent` ([#9595](MetaMask/core#9595)) ``` ## **Changelog**  CHANGELOG entry: null ## **Related issues** Related: https://consensyssoftware.atlassian.net/browse/WPN-1710 ## **Manual testing steps** 1. Verify the network switching and asset polling work same as before ## **Screenshots/Recordings**  ### **Before**  ### **After**  ## **Pre-merge author checklist** - [ ] I've followed [MetaMask Contributor Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask Extension Coding Standards](https://github.com/MetaMask/metamask-extension/blob/main/.github/guidelines/CODING_GUIDELINES.md). - [ ] I've completed the PR template to the best of my ability - [ ] I’ve included tests if applicable - [ ] I’ve documented my code using [JSDoc](https://jsdoc.app/) format if applicable - [ ] I’ve applied the right labels on the PR (see [labeling guidelines](https://github.com/MetaMask/metamask-extension/blob/main/.github/guidelines/LABELING_GUIDELINES.md)). Not required for external contributors. ## **Pre-merge reviewer checklist** - [ ] I've manually tested the PR (e.g. pull and build branch, run the app, test code being changed). - [ ] I confirm that this PR addresses all acceptance criteria described in the ticket it closes and includes the necessary testing evidence such as recordings and or screenshots.  --- > [!NOTE] > **Medium Risk** > Popular-network behavior now depends on config registry state at runtime; incorrect messenger wiring would break network enablement, but the change is limited to dependency versions and one delegate action. > > **Overview** > Bumps **`@metamask/network-enablement-controller`** to `^6.0.0` and **`@metamask/config-registry-controller`** to `^1.0.0`, with lockfile updates. > > Wires **`NetworkEnablementController`** to the config registry by delegating **`ConfigRegistryController:getState`** on its messenger so v6 can use registry data for popular-network classification. > > Config-registry selector tests now build mock registry entries with the **`RegistryNetworkConfig`** type instead of untyped inline objects, matching the v1 typed `configs.networks` shape. > > <sup>Reviewed by [Cursor Bugbot](https://cursor.com/bugbot) for commit 1ddf8cd. Bugbot is set up for automated code reviews on this repo. Configure [here](https://www.cursor.com/dashboard/bugbot).</sup>  --------- Co-authored-by: MetaMask Bot <metamaskbot@users.noreply.github.com> Co-authored-by: Guillaume Roux <guillaumeroux123@gmail.com>

FrederikBolding added 2 commits July 6, 2026 14:56

Initialize Release 1094.0.0

f300e18

Update Release 1094.0.0

6790c3b

FrederikBolding requested review from a team as code owners July 6, 2026 12:58

FrederikBolding temporarily deployed to default-branch July 6, 2026 12:58 — with GitHub Actions Inactive

FrederikBolding temporarily deployed to default-branch July 6, 2026 12:59 — with GitHub Actions Inactive

chore: Update dependency bump changelog entries

41a142d

cryptodev-2s approved these changes Jul 6, 2026

View reviewed changes

FrederikBolding enabled auto-merge July 6, 2026 13:03

wenfix approved these changes Jul 6, 2026

View reviewed changes

FrederikBolding added this pull request to the merge queue Jul 6, 2026

Merged via the queue into main with commit 52f6d08 Jul 6, 2026
412 of 413 checks passed

FrederikBolding deleted the release/1094.0.0 branch July 6, 2026 13:07

cloudonshore mentioned this pull request Jul 7, 2026

Release 1102.0.0 #9421

Merged

3 tasks done

This was referenced Jul 8, 2026

bump: upgrade @metamask/assets-controller to ^10.1.0 MetaMask/metamask-extension#44246

Merged

chore: bump @metamask/assets-controller to ^10.1.0 MetaMask/metamask-mobile#32950

Merged

cursor Bot mentioned this pull request Jul 8, 2026

Memory Update: [ADD] Pin @metamask/messenger v2 transitive requests to v1.2.0 until client migrates Prithpal-Sooriya/Cloud-Agent-Memory#44

Closed

ffmcgee725 mentioned this pull request Jul 22, 2026

Release/1137.0.0 #9592

Merged

4 tasks

Navigation Menu

Uh oh!

Release 1094.0.0 - #9392

Release 1094.0.0#9392
FrederikBolding merged 3 commits into
mainfrom
release/1094.0.0

FrederikBolding commented Jul 6, 2026 •

edited by cursor Bot

Loading

Uh oh!

metamask-ci Bot commented Jul 6, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Uh oh!

Conversation

FrederikBolding commented Jul 6, 2026 • edited by cursor Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Explanation

Uh oh!

metamask-ci Bot commented Jul 6, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

FrederikBolding commented Jul 6, 2026 •

edited by cursor Bot

Loading