Release/892.0.0

[infiniteflower]

Explanation

This releases BridgeController, BridgeStatusController and TransactionPayController

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 a release/version bump, but it publishes @metamask/bridge-controller@70.0.0, which includes a breaking state shape addition (quoteStreamComplete) that downstream consumers must handle.

Overview
Release bump across bridge-related packages. This increments the monorepo version to 892.0.0 and releases @metamask/bridge-controller to 70.0.0 (documenting a breaking new quoteStreamComplete field on BridgeControllerState).

Downstream packages are revved to consume the new bridge-controller release: @metamask/bridge-status-controller to 70.0.4 and @metamask/transaction-pay-controller to 19.0.1, updating their dependency ranges and yarn.lock accordingly.

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

[mcmire]

Sorry one more thing. What is breaking about this dependency bump, i.e., what change needs to be made in either the extension or mobile app to accommodate this change (assuming that change has not already been made)? Or, does this dependency bump cause any incompatible changes to types exported by this package? It would be helpful to explain this, if only for posterity.

(Same for transaction-pay-controller)

[infiniteflower]

The main thing is that bridge-controller has a new state field and if we bump the version on the clients then the E2E tests will break due to this new non-optional field.

[mcmire]

That seems like that describes the breaking change for bridge-controller. You can't upgrade this package in a client without needing to add a migration or update the tests. But if you just upgraded bridge-status-controller in a client without also upgrading bridge-controller, would the e2e tests break or would CI fail in some other way? Or same for transaction-pay-controller?

[mcmire]

LGTM!