Skip to content

Conversation

@micaelae
Copy link
Member

@micaelae micaelae commented Nov 26, 2025

Explanation

Publishes QuotesReceived event through BridgeController when quote polling stops on submit to ensure it happens before navigation resets the state

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

Routes QuotesReceived publishing through BridgeController when polling stops on submit; submitTx now passes context; adds TransactionSubmitted abort reason and improves logging.

  • Bridge Controller:
    • Update stopPollingForQuotes(reason?, context?) to optionally publish Unified SwapBridge Quotes Received if quotes are still loading before abort; accept AbortReason and metric context.
    • Add AbortReason.TransactionSubmitted; ignore it in fetch error early-returns; export AbortReason.
    • Improve error log to include eventName in trackUnifiedSwapBridgeEvent catch.
  • Bridge Status Controller:
    • Change submitTx signature to accept quotesReceivedContext and call BridgeController:stopPollingForQuotes(AbortReason.TransactionSubmitted, context) instead of publishing QuotesReceived directly.
    • Narrow #trackUnifiedSwapBridgeEvent generic to exclude QuotesReceived.
  • Tests/Changelogs:
    • Update snapshots and tests to reflect new stopPolling parameters and event routing.
    • Document behavior changes in both packages’ CHANGELOGs.

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

@micaelae micaelae requested a review from a team as a code owner November 26, 2025 01:20
@micaelae
Copy link
Member Author

@metamaskbot publish-preview

@github-actions
Copy link
Contributor

Preview builds have been published. See these instructions for more information about preview builds.

Expand for full list of packages and versions.
{
  "@metamask-previews/account-tree-controller": "4.0.0-preview-d21b3dc",
  "@metamask-previews/accounts-controller": "35.0.0-preview-d21b3dc",
  "@metamask-previews/address-book-controller": "7.0.1-preview-d21b3dc",
  "@metamask-previews/analytics-controller": "0.0.0-preview-d21b3dc",
  "@metamask-previews/announcement-controller": "8.0.0-preview-d21b3dc",
  "@metamask-previews/app-metadata-controller": "2.0.0-preview-d21b3dc",
  "@metamask-previews/approval-controller": "8.0.0-preview-d21b3dc",
  "@metamask-previews/assets-controllers": "91.0.0-preview-d21b3dc",
  "@metamask-previews/base-controller": "9.0.0-preview-d21b3dc",
  "@metamask-previews/bridge-controller": "63.1.0-preview-d21b3dc",
  "@metamask-previews/bridge-status-controller": "63.0.0-preview-d21b3dc",
  "@metamask-previews/build-utils": "3.0.4-preview-d21b3dc",
  "@metamask-previews/chain-agnostic-permission": "1.2.2-preview-d21b3dc",
  "@metamask-previews/claims-controller": "0.2.0-preview-d21b3dc",
  "@metamask-previews/composable-controller": "12.0.0-preview-d21b3dc",
  "@metamask-previews/controller-utils": "11.16.0-preview-d21b3dc",
  "@metamask-previews/core-backend": "5.0.0-preview-d21b3dc",
  "@metamask-previews/delegation-controller": "2.0.0-preview-d21b3dc",
  "@metamask-previews/earn-controller": "11.0.0-preview-d21b3dc",
  "@metamask-previews/eip-5792-middleware": "2.0.0-preview-d21b3dc",
  "@metamask-previews/eip-7702-internal-rpc-middleware": "0.1.0-preview-d21b3dc",
  "@metamask-previews/eip1193-permission-middleware": "1.0.2-preview-d21b3dc",
  "@metamask-previews/ens-controller": "19.0.0-preview-d21b3dc",
  "@metamask-previews/error-reporting-service": "3.0.0-preview-d21b3dc",
  "@metamask-previews/eth-block-tracker": "15.0.0-preview-d21b3dc",
  "@metamask-previews/eth-json-rpc-middleware": "22.0.0-preview-d21b3dc",
  "@metamask-previews/eth-json-rpc-provider": "6.0.0-preview-d21b3dc",
  "@metamask-previews/foundryup": "1.0.1-preview-d21b3dc",
  "@metamask-previews/gas-fee-controller": "26.0.0-preview-d21b3dc",
  "@metamask-previews/gator-permissions-controller": "0.6.0-preview-d21b3dc",
  "@metamask-previews/json-rpc-engine": "10.2.0-preview-d21b3dc",
  "@metamask-previews/json-rpc-middleware-stream": "8.0.8-preview-d21b3dc",
  "@metamask-previews/keyring-controller": "25.0.0-preview-d21b3dc",
  "@metamask-previews/logging-controller": "7.0.1-preview-d21b3dc",
  "@metamask-previews/message-manager": "14.1.0-preview-d21b3dc",
  "@metamask-previews/messenger": "0.3.0-preview-d21b3dc",
  "@metamask-previews/multichain-account-service": "4.0.0-preview-d21b3dc",
  "@metamask-previews/multichain-api-middleware": "1.2.4-preview-d21b3dc",
  "@metamask-previews/multichain-network-controller": "3.0.0-preview-d21b3dc",
  "@metamask-previews/multichain-transactions-controller": "7.0.0-preview-d21b3dc",
  "@metamask-previews/name-controller": "9.0.0-preview-d21b3dc",
  "@metamask-previews/network-controller": "26.0.0-preview-d21b3dc",
  "@metamask-previews/network-enablement-controller": "4.0.0-preview-d21b3dc",
  "@metamask-previews/notification-services-controller": "21.0.0-preview-d21b3dc",
  "@metamask-previews/permission-controller": "12.1.1-preview-d21b3dc",
  "@metamask-previews/permission-log-controller": "5.0.0-preview-d21b3dc",
  "@metamask-previews/phishing-controller": "16.1.0-preview-d21b3dc",
  "@metamask-previews/polling-controller": "16.0.0-preview-d21b3dc",
  "@metamask-previews/preferences-controller": "22.0.0-preview-d21b3dc",
  "@metamask-previews/profile-sync-controller": "27.0.0-preview-d21b3dc",
  "@metamask-previews/rate-limit-controller": "7.0.0-preview-d21b3dc",
  "@metamask-previews/remote-feature-flag-controller": "2.0.1-preview-d21b3dc",
  "@metamask-previews/sample-controllers": "4.0.0-preview-d21b3dc",
  "@metamask-previews/seedless-onboarding-controller": "7.0.0-preview-d21b3dc",
  "@metamask-previews/selected-network-controller": "26.0.0-preview-d21b3dc",
  "@metamask-previews/shield-controller": "3.0.0-preview-d21b3dc",
  "@metamask-previews/signature-controller": "37.0.0-preview-d21b3dc",
  "@metamask-previews/subscription-controller": "5.0.0-preview-d21b3dc",
  "@metamask-previews/token-search-discovery-controller": "4.0.0-preview-d21b3dc",
  "@metamask-previews/transaction-controller": "62.3.0-preview-d21b3dc",
  "@metamask-previews/transaction-pay-controller": "10.1.0-preview-d21b3dc",
  "@metamask-previews/user-operation-controller": "41.0.0-preview-d21b3dc"
}

@micaelae micaelae requested a review from a team as a code owner November 26, 2025 04:03
@micaelae micaelae enabled auto-merge November 26, 2025 05:40
@micaelae micaelae added this pull request to the merge queue Nov 26, 2025
Merged via the queue into main with commit 61d1bb0 Nov 26, 2025
274 checks passed
@micaelae micaelae deleted the swaps-move-received-event branch November 26, 2025 05:48
@micaelae micaelae mentioned this pull request Nov 26, 2025
4 tasks
github-merge-queue bot pushed a commit that referenced this pull request Nov 26, 2025
## Explanation

Releasing this PR: #7242

<!--
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

- [x] I've updated the test suite for new or updated code as appropriate
- [x] I've updated documentation (JSDoc, Markdown, etc.) for new or
updated code as appropriate
- [x] 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)
- [x] I've introduced [breaking
changes](https://github.com/MetaMask/core/tree/main/docs/breaking-changes.md)
in this PR and have prepared draft pull requests for clients and
consumer packages to resolve them

<!-- CURSOR_SUMMARY -->
---

> [!NOTE]
> Publishes bridge-controller 63.2.0 (metrics context in
stopPollingForQuotes) and bumps dependent packages, updating monorepo to
695.0.0.
> 
> - **Release**:
>   - Bump monorepo to `695.0.0`.
> - **@metamask/bridge-controller (63.2.0)**:
> - `stopPollingForQuotes` accepts metrics context; if quotes still
loading, publishes `Unified SwapBridge Quotes Received` before cancel.
> - **Dependencies/Consumers**:
> - `@metamask/bridge-status-controller` → depend on
`@metamask/bridge-controller@^63.2.0` and release `63.1.0`.
> - `@metamask/transaction-pay-controller` → bump to
`@metamask/bridge-controller@^63.2.0` and
`@metamask/bridge-status-controller@^63.1.0`.
>   - Update `yarn.lock` accordingly.
> 
> <sup>Written by [Cursor
Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit
dae09f3. This will update automatically
on new commits. Configure
[here](https://cursor.com/dashboard?tab=bugbot).</sup>
<!-- /CURSOR_SUMMARY -->
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.

3 participants