Skip to content

Release 1094.0.0 - #9392

Merged
FrederikBolding merged 3 commits into
mainfrom
release/1094.0.0
Jul 6, 2026
Merged

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

Conversation

@FrederikBolding

@FrederikBolding FrederikBolding commented Jul 6, 2026 •
edited by cursor Bot
Loading

Copy link
Copy Markdown
Member

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.

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

metamask-ci Bot commented Jul 6, 2026

Copy link
Copy Markdown

✅ Changelogs updated and pushed.

@FrederikBolding
FrederikBolding enabled auto-merge July 6, 2026 13:03
@FrederikBolding
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
FrederikBolding deleted the release/1094.0.0 branch July 6, 2026 13:07
@cloudonshore cloudonshore mentioned this pull request Jul 7, 2026
Merged
3 tasks
pull Bot pushed a commit to dmrazzy/core that referenced this pull request Jul 7, 2026
@cloudonshore @github-actions
Release 1102.0.0 (MetaMask#9421)
6b38b9a 
## Explanation

Releases two packages needed to fix stuck/underpriced bridge smart
transactions in the clients (extension + mobile).

### `@metamask/transaction-controller` — `68.2.2` → `68.3.0` (minor)
- **Added:** `failTransaction` method +
`TransactionController:failTransaction` messenger action
([MetaMask#9400](MetaMask#9400)) — fails a tx
through the standard path, emitting
`transactionFailed`/`transactionStatusUpdated`/`transactionFinished`.
- **Fixed:** Only apply user-saved (advanced) gas fees to dApp
transactions; ignored for internal (`isInternal`) txs such as swaps and
bridges ([MetaMask#9401](MetaMask#9401)).
- **Changed:** Bump `@metamask/messenger` `^1.2.0` → `^2.0.0`
([MetaMask#9392](MetaMask#9392)).

### `@metamask/smart-transactions-controller` — `24.2.4` → `25.0.0`
(major)
- **Changed (BREAKING):** Fail the associated regular transaction via
`TransactionController:failTransaction` instead of `updateTransaction`
when a smart transaction is cancelled
([MetaMask#9400](MetaMask#9400)). Consumers must
now grant the STX messenger access to
`TransactionController:failTransaction`.
- **Changed:** Bump `@metamask/messenger` `^1.2.0` → `^2.0.0`
([MetaMask#9392](MetaMask#9392)).

All other changed packages are `intentionally-skip` (owned by other
teams); dependent version ranges were updated automatically.

## References

- Fixes stuck-pending bridge STX (root cause in MetaMask#9400) and underpriced
bridge gas (MetaMask#9401).

## Checklist

- [x] I've followed the [release
process](https://github.com/MetaMask/core/blob/main/docs/processes/releasing.md)
- [x] Changelogs reviewed and categorized (no `Uncategorized`; breaking
change marked)
- [x] Version bumps follow SemVer (STX major for the breaking messenger
change)

<!-- CURSOR_SUMMARY -->
---

> [!NOTE]
> **Medium Risk**
> Touches transaction failure signaling and gas on internal bridge
flows; STX **25.0.0** is a breaking messenger permission change for
extension/mobile integrators.
> 
> **Overview**
> **Monorepo release `1102.0.0`** that publishes
**`@metamask/transaction-controller` `68.3.0`** and
**`@metamask/smart-transactions-controller` `25.0.0`**, and rolls
**`@metamask/transaction-controller` `^68.2.2` → `^68.3.0`** through
dependent packages and **`yarn.lock`**.
> 
> **`transaction-controller` `68.3.0`** (documented in its changelog for
this release): adds **`failTransaction`** /
**`TransactionController:failTransaction`** so out-of-band failures emit
normal lifecycle events; fixes **advanced gas fees** so they apply only
to dApp txs, not **`isInternal`** bridge/swap txs.
> 
> **`smart-transactions-controller` `25.0.0` (breaking):** on smart-tx
cancel, calls **`failTransaction`** instead of **`updateTransaction`**;
hosts must delegate **`TransactionController:failTransaction`** on the
STX messenger.
> 
> Other touched packages in the diff are mainly **version/changelog
dependency bumps** tied to this release, not new feature code in those
files.
> 
> <sup>Reviewed by [Cursor Bugbot](https://cursor.com/bugbot) for commit
c423a08. Bugbot is set up for automated
code reviews on this repo. Configure
[here](https://www.cursor.com/dashboard/bugbot).</sup>
<!-- /CURSOR_SUMMARY -->

---------

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
This was referenced Jul 8, 2026
Merged
Merged
@cursor cursor Bot mentioned this pull request Jul 8, 2026
Closed
pull Bot pushed a commit to Eric-Johnson-1/metamask-extension that referenced this pull request Jul 8, 2026
@Prithpal-Sooriya
bump: upgrade @metamask/assets-controller to ^10.1.0 (MetaMask#44246
9ef5547 
)

<!-- CURSOR_AGENT_PR_BODY_BEGIN -->
## **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.

<!--
## **Screenshots/Recordings**

### **Before**

### **After**
-->

## **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.
<!-- CURSOR_AGENT_PR_BODY_END -->

<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>&nbsp;<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>&nbsp;</div>
pull Bot pushed a commit to Reality2byte/metamask-mobile that referenced this pull request Jul 8, 2026
@Prithpal-Sooriya
chore: bump @metamask/assets-controller to ^10.1.0 (MetaMask#32950)
9a6864e 
<!-- CURSOR_AGENT_PR_BODY_BEGIN -->
## **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**

<!-- [screenshots/recordings] -->

### **After**

<!-- [screenshots/recordings] -->

## **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.
<!-- CURSOR_AGENT_PR_BODY_END -->

<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>&nbsp;<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>&nbsp;</div>
@ffmcgee725 ffmcgee725 mentioned this pull request Jul 22, 2026
Merged
4 tasks
pull Bot pushed a commit to dmrazzy/core that referenced this pull request Jul 22, 2026
@ffmcgee725 @github-actions
Release/1137.0.0 (MetaMask#9592)
8f3da61 
## @metamask/money-account-api-data-service

## [0.3.0]

### Added

- Add optional `trace` callback to `MoneyAccountApiDataService`
constructor for network request tracing
([MetaMask#9451](MetaMask#9451))
- All HTTP calls (`fetchPositions`, `fetchInterest`, `fetchHistory`,
`fetchRateHistory`) emit best-effort backdated traces with `startTime`,
`success`, and `errorName` attributes
- Tracing is isolated from fetch/retry logic; trace failures do not
impact queries

## @metamask/chomp-api-service

## [4.0.0]

### Added

- Add `getAssociatedAddresses` method, exposed as the
`ChompApiService:getAssociatedAddresses` messenger action, which fetches
the active address associations of the authenticated profile via `GET
/v1/auth/address` ([MetaMask#9387](MetaMask#9387))
- Also adds the `ProfileAddressEntry` type describing each returned
entry and the `ChompApiServiceGetAssociatedAddressesAction` type
- Returned addresses are parsed into canonical lowercase form, entries
are guaranteed to have `status: 'active'`, and results are never served
from cache
- The query cache key is scoped to the authenticated profile via a
SHA-256 digest of the bearer token, so concurrent calls only share an
in-flight request when they are for the same profile and one profile's
associations are never cached under another's key

### Changed

- **BREAKING:** `associateAddress` now throws an `HttpError` on a 409
response instead of returning the parsed body
([MetaMask#9387](MetaMask#9387))
- A 409 from `POST /v1/auth/address` indicates the address is associated
with a _different_ profile; the previous handling attempted to parse the
error body as an association result and failed with a confusing
validation error. An address already associated with the authenticated
profile is reported via a 201 response with `status: 'active'`, which is
unchanged.
- Bump `@metamask/utils` from `^11.9.0` to `^11.11.0`
([MetaMask#9074](MetaMask#9074))
- Bump `@metamask/controller-utils` from `^12.0.0` to `^12.3.0`
([MetaMask#8774](MetaMask#8774),
[MetaMask#9058](MetaMask#9058),
[MetaMask#9083](MetaMask#9083),
[MetaMask#9218](MetaMask#9218))
- Bump `@metamask/base-data-service` from `^0.1.2` to `^0.1.3`
([MetaMask#8799](MetaMask#8799))
- Bump `@metamask/messenger` from `^1.2.0` to `^2.0.0`
([MetaMask#9392](MetaMask#9392))
- Update `LICENSE` text
([MetaMask#9472](MetaMask#9472))

## @metamask/money-account-upgrade-controller

## [3.0.0]

- **BREAKING:** Add persisted state tracking fully upgraded accounts
([MetaMask#9500](MetaMask#9500))
- `MoneyAccountUpgradeControllerState` changes from `Record<string,
never>` to `{ upgradedAccounts }`, keyed by lowercased account address.
Each entry records when the upgrade sequence completed and a fingerprint
of the config it completed under (see new `MoneyAccountUpgradeStatus`
type). Code constructing the state type (e.g. `{}` in tests or
default-state maps) must include `upgradedAccounts`.
- The constructor now accepts an optional `state` option, merged with
the defaults; add `getDefaultMoneyAccountUpgradeControllerState` to
construct those defaults.
- Add `TerminalUpgradeError` and `isTerminalMoneyAccountUpgradeError`,
and a `terminal` property on `MoneyAccountUpgradeStepError`, marking
failures that cannot resolve by retrying — currently an account
delegated to a third-party EIP-7702 implementation, an account with
unexpected on-chain code, or an address confirmed to be associated with
a different CHOMP profile
([MetaMask#9500](MetaMask#9500))
- The controller does not retry on its own; clients implementing their
own retry logic around `upgradeAccount` can use
`isTerminalMoneyAccountUpgradeError` to stop retrying failures that
cannot succeed.

### Changed

- **BREAKING:** The `associate-address` upgrade step now checks the
profile's existing address associations via
`ChompApiService:getAssociatedAddresses` before signing, and reports
`already-done` without signing or submitting anything when the address
is already associated
([MetaMask#9387](MetaMask#9387))
- `MoneyAccountUpgradeControllerMessenger` consumers must grant the
`ChompApiService:getAssociatedAddresses` action alongside the previously
required actions, and must provide a `@metamask/chomp-api-service`
version that registers it (`>=4.0.0`).
- The lookup is an optimization: if it fails, the step falls through to
the previous sign-and-submit behavior.
- A 409 conflict from the association request is disambiguated by
re-fetching the associations, so a same-profile create race reports
`already-done` instead of failing the upgrade; a genuine conflict
(address associated with a different profile) still fails the step.
- `upgradeAccount` now skips the step sequence entirely when the account
is recorded in state as upgraded under the active config fingerprint,
and records the account after a successful run. If the chain, CHOMP
contract addresses, or Delegation Framework version change, the
fingerprint no longer matches and the sequence re-runs
([MetaMask#9500](MetaMask#9500))
- Bump `@metamask/messenger` from `^1.2.0` to `^2.0.0`
([MetaMask#9392](MetaMask#9392))
- Bump `@metamask/authenticated-user-storage` from `^3.0.0` to `^3.0.1`
([MetaMask#9458](MetaMask#9458))
- Bump `@metamask/chomp-api-service` from `^3.1.0` to `^4.0.0`
([MetaMask#9586](MetaMask#9586))

<!--
Thanks for your contribution! Take a moment to answer these questions so
that reviewers have the information they need to properly understand
your changes:

* What is the current state of things and why does it need to change?
* What is the solution your changes offer and how does it work?
* Are there any changes whose purpose might not obvious to those
unfamiliar with the domain?
* If your primary goal was to update one package but you found you had
to update another one along the way, why did you do so?
* If you had to upgrade a dependency, why did you do so?
-->

## References

<!--
Are there any issues that this pull request is tied to?
Are there other links that reviewers should consult to understand these
changes better?
Are there client or consumer pull requests to adopt any breaking
changes?

For example:

* Fixes #12345
* Related to #67890
-->

## Checklist

- [ ] I've updated the test suite for new or updated code as appropriate
- [ ] I've updated documentation (JSDoc, Markdown, etc.) for new or
updated code as appropriate
- [ ] I've communicated my changes to consumers by [updating changelogs
for packages I've
changed](https://github.com/MetaMask/core/tree/main/docs/processes/updating-changelogs.md)
- [ ] I've introduced [breaking
changes](https://github.com/MetaMask/core/tree/main/docs/processes/breaking-changes.md)
in this PR and have prepared draft pull requests for clients and
consumer packages to resolve them

<!-- CURSOR_SUMMARY -->
---

> [!NOTE]
> **High Risk**
> Multiple breaking releases affect CHOMP address association error
handling and Money account upgrade state/messenger permissions;
consumers must adopt new versions and migration steps together.
> 
> **Overview**
> **Monorepo release `1137.0.0`** — version bumps, finalized changelogs,
and `yarn.lock` alignment for Money/CHOMP packages (no new
implementation in this diff beyond release metadata).
> 
> **`@metamask/chomp-api-service@4.0.0` (breaking):** ships
`getAssociatedAddresses` and changes **`associateAddress`** to **throw
on HTTP 409** instead of parsing the error body.
> 
> **`@metamask/money-account-upgrade-controller@3.0.0` (breaking):**
persisted **`upgradedAccounts`** state (config fingerprint), **terminal
upgrade errors**, associate-address pre-check via
**`getAssociatedAddresses`**, and **409 disambiguation**; depends on
**`chomp-api-service@^4.0.0`**.
> 
> **`@metamask/money-account-api-data-service@0.3.0`:** optional
constructor **`trace`** callback for Money API HTTP calls.
**`money-account-balance-service`** only bumps that dependency to
`^0.3.0` (changelog under Unreleased; no package version bump in this
diff).
> 
> <sup>Reviewed by [Cursor Bugbot](https://cursor.com/bugbot) for commit
edd0ba1. Bugbot is set up for automated
code reviews on this repo. Configure
[here](https://www.cursor.com/dashboard/bugbot).</sup>
<!-- /CURSOR_SUMMARY -->

---------

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
pull Bot pushed a commit to firas9941/metamask-extension that referenced this pull request Aug 4, 2026
@mikesposito @metamaskbot @GuillaumeRx
chore: bump `@metamask/{network-enablement, config-registry}-controll…
aedce77 
…er` (MetaMask#44766)

<!--
Please submit this PR as a draft initially.
Do not mark it as "Ready for review" until the template has been
completely filled out, and PR status checks have passed at least once.
-->

## **Description**

<!--
Write a short description of the changes included in this pull request,
also include relevant motivation and context. Have in mind the following
questions:
1. What is the reason for the change?
2. What is the improvement/solution?
-->
~~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**

<!--
If this PR is not End-User-Facing and should not show up in the
CHANGELOG, you can choose to either:
1. Write `CHANGELOG entry: null`
2. Label with `no-changelog`

If this PR is End-User-Facing, please write a short User-Facing
description in the past tense like:
`CHANGELOG entry: Added a new tab for users to see their NFTs`
`CHANGELOG entry: Fixed a bug that was causing some NFTs to flicker`

(This helps the Release Engineer do their job more quickly and
accurately)
-->

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**

<!-- If applicable, add screenshots and/or recordings to visualize the
before and after of your change. -->

### **Before**

<!-- [screenshots/recordings] -->

### **After**

<!-- [screenshots/recordings] -->

## **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.

<!-- CURSOR_SUMMARY -->
---

> [!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>
<!-- /CURSOR_SUMMARY -->

---------

Co-authored-by: MetaMask Bot <metamaskbot@users.noreply.github.com>
Co-authored-by: Guillaume Roux <guillaumeroux123@gmail.com>
n3ps pushed a commit to MetaMask/metamask-extension that referenced this pull request Aug 5, 2026
@mikesposito @metamaskbot
@GuillaumeRx @n3ps
chore: bump `@metamask/{network-enablement, config-registry}-controll…
9020f85 
…er` (#44766)

<!--
Please submit this PR as a draft initially.
Do not mark it as "Ready for review" until the template has been
completely filled out, and PR status checks have passed at least once.
-->

## **Description**

<!--
Write a short description of the changes included in this pull request,
also include relevant motivation and context. Have in mind the following
questions:
1. What is the reason for the change?
2. What is the improvement/solution?
-->
~~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**

<!--
If this PR is not End-User-Facing and should not show up in the
CHANGELOG, you can choose to either:
1. Write `CHANGELOG entry: null`
2. Label with `no-changelog`

If this PR is End-User-Facing, please write a short User-Facing
description in the past tense like:
`CHANGELOG entry: Added a new tab for users to see their NFTs`
`CHANGELOG entry: Fixed a bug that was causing some NFTs to flicker`

(This helps the Release Engineer do their job more quickly and
accurately)
-->

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**

<!-- If applicable, add screenshots and/or recordings to visualize the
before and after of your change. -->

### **Before**

<!-- [screenshots/recordings] -->

### **After**

<!-- [screenshots/recordings] -->

## **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.

<!-- CURSOR_SUMMARY -->
---

> [!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>
<!-- /CURSOR_SUMMARY -->

---------

Co-authored-by: MetaMask Bot <metamaskbot@users.noreply.github.com>
Co-authored-by: Guillaume Roux <guillaumeroux123@gmail.com>
Bigshmow pushed a commit to MetaMask/metamask-extension that referenced this pull request Aug 5, 2026
@mikesposito @metamaskbot @GuillaumeRx
chore: bump `@metamask/{network-enablement, config-registry}-controll…
53f743a 
…er` (#44766)

<!--
Please submit this PR as a draft initially.
Do not mark it as "Ready for review" until the template has been
completely filled out, and PR status checks have passed at least once.
-->

## **Description**

<!--
Write a short description of the changes included in this pull request,
also include relevant motivation and context. Have in mind the following
questions:
1. What is the reason for the change?
2. What is the improvement/solution?
-->
~~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**

<!--
If this PR is not End-User-Facing and should not show up in the
CHANGELOG, you can choose to either:
1. Write `CHANGELOG entry: null`
2. Label with `no-changelog`

If this PR is End-User-Facing, please write a short User-Facing
description in the past tense like:
`CHANGELOG entry: Added a new tab for users to see their NFTs`
`CHANGELOG entry: Fixed a bug that was causing some NFTs to flicker`

(This helps the Release Engineer do their job more quickly and
accurately)
-->

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**

<!-- If applicable, add screenshots and/or recordings to visualize the
before and after of your change. -->

### **Before**

<!-- [screenshots/recordings] -->

### **After**

<!-- [screenshots/recordings] -->

## **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.

<!-- CURSOR_SUMMARY -->
---

> [!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>
<!-- /CURSOR_SUMMARY -->

---------

Co-authored-by: MetaMask Bot <metamaskbot@users.noreply.github.com>
Co-authored-by: Guillaume Roux <guillaumeroux123@gmail.com>
n3ps pushed a commit to MetaMask/metamask-extension that referenced this pull request Aug 6, 2026
@mikesposito @metamaskbot
@GuillaumeRx @n3ps
chore: bump `@metamask/{network-enablement, config-registry}-controll…
c7e12cb 
…er` (#44766)

<!--
Please submit this PR as a draft initially.
Do not mark it as "Ready for review" until the template has been
completely filled out, and PR status checks have passed at least once.
-->

## **Description**

<!--
Write a short description of the changes included in this pull request,
also include relevant motivation and context. Have in mind the following
questions:
1. What is the reason for the change?
2. What is the improvement/solution?
-->
~~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**

<!--
If this PR is not End-User-Facing and should not show up in the
CHANGELOG, you can choose to either:
1. Write `CHANGELOG entry: null`
2. Label with `no-changelog`

If this PR is End-User-Facing, please write a short User-Facing
description in the past tense like:
`CHANGELOG entry: Added a new tab for users to see their NFTs`
`CHANGELOG entry: Fixed a bug that was causing some NFTs to flicker`

(This helps the Release Engineer do their job more quickly and
accurately)
-->

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**

<!-- If applicable, add screenshots and/or recordings to visualize the
before and after of your change. -->

### **Before**

<!-- [screenshots/recordings] -->

### **After**

<!-- [screenshots/recordings] -->

## **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.

<!-- CURSOR_SUMMARY -->
---

> [!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>
<!-- /CURSOR_SUMMARY -->

---------

Co-authored-by: MetaMask Bot <metamaskbot@users.noreply.github.com>
Co-authored-by: Guillaume Roux <guillaumeroux123@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@wenfix wenfix wenfix approved these changes
@cryptodev-2s cryptodev-2s cryptodev-2s approved these changes

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@FrederikBolding @wenfix @cryptodev-2s