[mikesposito]

New release for @metamask/config-registry-controller + dependents

---

Note

Medium Risk
Medium risk from cascading a major @metamask/config-registry-controller bump and refreshed network-stack versions across many packages; impact is mostly dependency alignment, but consumers must handle the config-registry API breaking changes.

Overview
Release 1418.0.0 cuts coordinated version and dependency updates across the monorepo, centered on publishing @metamask/config-registry-controller@6.0.0 and propagating it through dependents.

The release bumps @metamask/network-controller to 38.0.1 (depends on config-registry 6.0.0 and analytics 4.3.1), @metamask/network-enablement-controller to 7.1.2, @metamask/analytics-controller to 4.3.1, @metamask/assets-controller to 20.4.0, and @metamask/wallet to 21.0.2. Dozens of other packages only update their package.json / changelogs to require network-controller@^38.0.1 (and related pins where applicable); yarn.lock and root package.json (1417 → 1418) reflect the same graph.

This PR does not introduce new feature code—it aligns versions so clients pick up config-registry-controller 6.0.0, whose breaking changes include FetchConfigResult / FetchEventsConfigResult using null instead of omitted fields and relaxed validation for RPC provider objects in network config fallbacks.

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

[mikesposito]

@metamaskbot update-changelogs

[metamask-ci]

✅ No changelog changes needed.