Release/857.0.0

[mathieuartu]

Explanation

• @metamask/profile-sync-controller 27.1.0 → 28.0.0
  • Major, breaking, reason for the other patch bumps in this release
• @metamask/profile-metrics-controller 3.0.2 → 3.0.3
  • Patch, contains a bugfix on top of the major the profile-sync bump
• @metamask/notification-services-controller 22.0.0 → 22.1.0
  • Minor, contains other fixes on top of the major profile-sync bump, seen with @Prithpal-Sooriya
• @metamask/subscription-controller 6.0.0 → 6.0.1
• @metamask/account-tree-controller 5.0.0 → 5.0.1
• @metamask/assets-controllers 100.2.0 → 100.2.1
• @metamask/bridge-controller 69.0.0 → 69.0.1
• @metamask/bridge-status-controller 68.0.1 → 68.0.2
• @metamask/claims-controller 0.4.2 → 0.4.3
• @metamask/config-registry-controller 0.1.0 → 0.1.1
• @metamask/core-backend 6.1.0 → 6.1.1
• @metamask/perps-controller 1.0.0 → 1.0.1

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
Primarily dependency/version churn, but it pulls in @metamask/profile-sync-controller@28.0.0 (major/breaking) across multiple controllers, which can introduce runtime or type incompatibilities for consumers.

Overview
Updates the monorepo release to 857.0.0 and publishes a coordinated set of patch/minor bumps across controllers to consume @metamask/profile-sync-controller@28.0.0 (e.g., account-tree-controller, assets-controllers, bridge-controller, bridge-status-controller, core-backend, subscription-controller, notification-services-controller, claims-controller, config-registry-controller, perps-controller).

Propagates the resulting transitive bumps (notably @metamask/assets-controllers@100.2.1, @metamask/core-backend@6.1.1, and bridge controller patches) into dependent packages (assets-controller, transaction-controller, transaction-pay-controller), with corresponding changelog entries and yarn.lock updates.

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

[socket-security]

No dependency changes detected. Learn more about Socket for GitHub.

👍 No dependency changes detected in pull request

[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.}

[mathieuartu]

@SocketSecurity ignore npm/@metamask/assets-controllers@100.2.0
@SocketSecurity ignore npm/@metamask/bridge-controller@69.0.0
@SocketSecurity ignore npm/@metamask/bridge-status-controller@68.0.1
@SocketSecurity ignore npm/@metamask/core-backend@6.1.0

The fetch usage seems warranted and pre-existing to this PR.

[ccharly]

LGTM for accounts