chore: bump network-controller and controller-utils cp-7.81.0#31128
Conversation
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
network-controller and controller-utilsnetwork-controller and controller-utils cp-7.81.0
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit b419982. Configure here.
🔍 Smart E2E Test Selection
click to see 🤖 AI reasoning detailsE2E Test Selection: Performance Test Selection: |

Description
Bumping
@metamask/network-controllerto^32.0.0and@metamask/controller-utilsto^12.1.0:Changelog
CHANGELOG entry: null
Related issues
Closes: https://consensyssoftware.atlassian.net/browse/WPN-1239
Manual testing steps
Screenshots/Recordings
Before
N/A
After
N/A
Pre-merge author checklist
Performance checks (if applicable)
trace()for usage andaddTokenfor an exampleFor performance guidelines and tooling, see the Performance Guide.
Pre-merge reviewer checklist
Note
Medium Risk
The breaking default-network removal can affect users or flows that relied on Avalanche, ZKSync, MegaETH, or Sei being preconfigured; otherwise this is primarily a dependency and test-fixture alignment change.
Overview
Bumps
@metamask/network-controllerto 32.0.0 and@metamask/controller-utilsto 12.1.0 (includingpackage.jsonresolutions andyarn.lock).That breaking network-controller release drops Sei, MegaETH, Avalanche, and ZKSync from built-in default EVM networks, so fresh installs no longer ship those chain configs unless users add them manually.
Test fixtures are aligned:
initial-background-state.jsonno longer seeds MegaETH, ZKSync, or Avalanche mainnet entries, andAddressSelector.test.tsxupdates the expected EVM-only network list to match.Reviewed by Cursor Bugbot for commit a8aa9b6. Bugbot is set up for automated code reviews on this repo. Configure here.