Release/650.0.0

[bergarces]

Explanation

Release for assets-controllers

Documented bump of @metamask/controller-utils on @metamask/assets-controllers and @metamask/networks-controllers, since they are the ones targeted by the change.

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, highlighting breaking changes as necessary
• I've prepared draft pull requests for clients and consumer packages to resolve any breaking changes

---

Note

Publishes controller-utils 11.15.0 and propagates it across packages; releases assets-controllers 85.0.0 and bridge/bridge-status-controller 57.0.0; bumps monorepo to 650.0.0.

• Releases:
  • assets-controllers@85.0.0: new features noted in changelog; bumps @metamask/controller-utils to ^11.15.0.
  • bridge-controller@57.0.0: updates peer/dev deps to @metamask/assets-controllers@^85.0.0.
  • bridge-status-controller@57.0.0: updates peer/dev deps to @metamask/bridge-controller@^57.0.0.
  • controller-utils@11.15.0: adds new Infura networks and related enums/constants.
• Deps:
  • Bump @metamask/controller-utils to ^11.15.0 across controllers and middleware packages.
• Repo:
  • Bump root version to 650.0.0 and update yarn.lock.

^{Written by Cursor Bugbot for commit b5dd262. This will update automatically on new commits. Configure here.}