Release/1310.0.0

[Kriys94]

Explanation

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
Two coordinated breaking releases (core-backend@12.0.0 API typing and assets-controller@18.0.0 messenger delegation) require client updates; incorrect adoption can break price filtering or leave multichain balance refresh silent.

Overview
This is a release cut for monorepo 1310.0.0: version bumps, changelog finalization, and yarn.lock updates across affected packages—no new application source in this diff.

@metamask/core-backend@12.0.0 is the main breaking dependency bump. Consumers must adopt the updated PriceSupportedNetworksResponse shape (partialSupport as { spotPricesV2; spotPricesV3 } instead of string[]). Downstream packages (assets-controller, assets-controllers, client-utils, social-controllers, transaction-controller, and others) now depend on ^12.0.0.

@metamask/assets-controller@18.0.0 is released with a breaking messenger requirement: apps must delegate MultichainTransactionsController:transactionConfirmed to the Assets messenger so Snap/non-EVM confirmations refresh balances. Changelog entries for 18.0.0 also document price-network filtering and v5 balance/scope fixes bundled in this release line.

Follow-on patch bumps wire the tree together: @metamask/assets-controllers@112.1.1, @metamask/bridge-controller@82.0.1, @metamask/transaction-pay-controller@30.0.1, @metamask/client-utils@3.0.4, and @metamask/social-controllers@3.5.0 (including SocialRealtimeService and the core-backend bump per its changelog).

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

[Kriys94]

@metamaskbot update-changelogs

[metamask-ci]

✅ No changelog changes needed.