Skip to content

Conversation

micaelae
Copy link
Member

@micaelae micaelae commented Oct 17, 2025

Explanation

Releases the bridge-controller and bridge-status-controller packages

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

Releases bridge-controller with a breaking constructor change and SSE flag update, and bridge-status-controller with fixes and dependency alignment; bumps monorepo to 628.0.0.

  • Packages:
    • packages/bridge-controller53.0.0:
      • BREAKING: require clientVersion in BridgeController constructor.
      • Update sseEnabled flag to include minimumVersion.
      • Bump deps: @metamask/network-controller/transaction-controller.
    • packages/bridge-status-controller51.0.1:
      • Fix Mobile crash after successful tx; fix unit test initialization.
      • Align peer/dev deps to @metamask/bridge-controller@^53.0.0.
      • Bump deps: @metamask/network-controller/transaction-controller.
  • Repo:
    • Bump root version to 628.0.0.

Written by Cursor Bugbot for commit 4e91f64. This will update automatically on new commits. Configure here.

@micaelae micaelae requested review from a team as code owners October 17, 2025 21:12
cursor[bot]

This comment was marked as outdated.

@micaelae micaelae enabled auto-merge (squash) October 17, 2025 21:24
@micaelae micaelae merged commit b6301b3 into main Oct 17, 2025
251 checks passed
@micaelae micaelae deleted the release/628.0.0 branch October 17, 2025 21:25
micaelae added a commit that referenced this pull request Oct 17, 2025
micaelae added a commit that referenced this pull request Oct 17, 2025
This reverts commit b6301b3.

## Explanation

<!--
Thanks for your contribution! Take a moment to answer these questions so
that reviewers have the information they need to properly understand
your changes:

* What is the current state of things and why does it need to change?
* What is the solution your changes offer and how does it work?
* Are there any changes whose purpose might not obvious to those
unfamiliar with the domain?
* If your primary goal was to update one package but you found you had
to update another one along the way, why did you do so?
* If you had to upgrade a dependency, why did you do so?
-->

## References

<!--
Are there any issues that this pull request is tied to?
Are there other links that reviewers should consult to understand these
changes better?
Are there client or consumer pull requests to adopt any breaking
changes?

For example:

* Fixes #12345
* Related to #67890
-->

## 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](https://github.com/MetaMask/core/tree/main/docs/contributing.md#updating-changelogs),
highlighting breaking changes as necessary
- [ ] I've prepared draft pull requests for clients and consumer
packages to resolve any breaking changes

<!-- CURSOR_SUMMARY -->
---

> [!NOTE]
> Reverts the 628.0.0 release by downgrading versions, removing latest
changelog sections, and aligning bridge-status-controller to
@metamask/bridge-controller ^52.0.0.
> 
> - **Release**:
>   - Downgrade root `package.json` version `628.0.0` → `627.0.0`.
> - **Packages**:
>   - `packages/bridge-controller`:
>     - Version `53.0.0` → `52.0.0`.
> - Remove `53.0.0` changelog entry; update `[Unreleased]` compare link
to start from `52.0.0`.
>   - `packages/bridge-status-controller`:
>     - Version `51.0.1` → `51.0.0`.
> - Remove `51.0.1` changelog entry; update `[Unreleased]` compare link
to start from `51.0.0`.
> - Downgrade `@metamask/bridge-controller` range in `devDependencies`
and `peerDependencies` to `^52.0.0`.
> - **Lockfile**:
> - Update `yarn.lock` to reflect `@metamask/bridge-controller@^52.0.0`.
> 
> <sup>Written by [Cursor
Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit
17aee70. This will update automatically
on new commits. Configure
[here](https://cursor.com/dashboard?tab=bugbot).</sup>
<!-- /CURSOR_SUMMARY -->
@cursor cursor bot mentioned this pull request Oct 17, 2025
4 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants