Release/1309.0.0

[micaelae]

Explanation

Releasing the @metamask/bridge-controller and @metamask/bridge-status-controller

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
The shipped breaking change renames a public FeatureId string/enum value, so MetaMask clients must adopt 82.0.0 and update any recurring_buy references before upgrading.

Overview
This is a release PR that bumps the monorepo to 1309.0.0 and publishes updated bridge packages—no application source changes appear in the diff itself.

@metamask/bridge-controller goes 81.4.0 → 82.0.0, with the changelog calling out a breaking rename of the FeatureId value from recurring_buy to recurring_order, plus a dependency bump on @metamask/assets-controllers to ^112.1.0.

@metamask/bridge-status-controller is released as 76.3.4, updating its dependency on @metamask/bridge-controller to ^82.0.0 and refreshing changelogs and yarn.lock accordingly.

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

[metamask-ci]

❌ Failed to push changelog fixes. Check the workflow run for details.