Release/653.0.0

[bergarces]

Explanation

assets-controller release

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 monorepo 653.0.0, releasing @metamask/assets-controllers@86 with AccountTrackerController changes and propagating breaking peer bumps to bridge-related packages (incl. fee flag update), plus yarn lock updates.

• Releases:
  • Bump monorepo to 653.0.0.
  • Publish @metamask/assets-controllers@86.0.0.
  • Publish @metamask/bridge-controller@58.0.0, @metamask/bridge-status-controller@58.0.0, @metamask/transaction-pay-controller@2.0.0.
• Assets Controllers (v86):
  • BREAKING: Update AccountTrackerController events/actions; add optional fetchingEnabled callback.
• Bridge Controller (v58):
  • BREAKING: Peer bump to @metamask/assets-controllers@^86.0.0.
  • BREAKING: Replace noFee request flag with fee flag.
• Bridge Status Controller (v58):
  • BREAKING: Peer bump to @metamask/bridge-controller@^58.0.0.
• Transaction Pay Controller (v2):
  • BREAKING: Peer bumps to @metamask/assets-controllers@^86.0.0, @metamask/bridge-controller@^58.0.0, and @metamask/bridge-status-controller@^58.0.0.
• Dependencies:
  • Align dev/peer deps and yarn.lock with new versions.

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

[Gudahtt]

LGTM!