Release 1157.0.0

[GuillaumeRx]

Explanation

This is a release for network-enablement-controller and all the dependent packages.

References

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
• I've introduced breaking changes in this PR and have prepared draft pull requests for clients and consumer packages to resolve them

---

Note

Medium Risk
No new code in the diff, but shipping network-enablement 6.0.0 and config-registry 1.0.0 propagates documented breaking messenger and state-shape changes to all dependents that adopt this release train.

Overview
Monorepo release 1157.0.0 with no runtime code edits in this PR—only version bumps, changelogs, package.json dependency ranges, and yarn.lock.

@metamask/network-enablement-controller 6.0.0 is the anchor release; dependents are republished to pull ^6.0.0 and aligned asset packages: assets-controller 11.3.1, assets-controllers 110.0.2, network-connection-banner-controller 0.1.1, plus bridge-controller and transaction-pay-controller dependency updates. @metamask/config-registry-controller is released as 1.0.0 and wired into network-enablement at ^1.0.0.

Consumers upgrading through this release inherit breaking changes already documented in those packages’ changelogs (e.g. network-enablement’s ConfigRegistryController:getState messenger requirement and config-registry networks keyed by Caip2ChainId), not new logic introduced here.

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

[GuillaumeRx]

@metamaskbot update-changelogs

[metamask-ci]

✅ Changelogs updated and pushed.

[cursor]

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 610d9a2. Configure here.}

[cryptodev-2s]

@mikesposito are we good to go v1 ? (cc @GuillaumeRx )

[GuillaumeRx]

It's starting to be used in network-enablement-controller. I consider that as being "ready for production" so I thought it should be bumped to v1