Merged
Conversation
| "@ethersproject/contracts": "^5.7.0", | ||
| "@ethersproject/providers": "^5.7.0", | ||
| "@metamask/assets-controller": "^4.0.0", | ||
| "@metamask/assets-controller": "^4.1.0", |
Contributor
There was a problem hiding this comment.
Do you need to bump transaction pay controller?
Prithpal-Sooriya
approved these changes
Apr 8, 2026
cryptodev-2s
approved these changes
Apr 8, 2026
github-merge-queue bot
pushed a commit
that referenced
this pull request
Apr 8, 2026
…8404) This reverts commit 31172c1 and 817fd03 ## 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/processes/updating-changelogs.md) - [ ] I've introduced [breaking changes](https://github.com/MetaMask/core/tree/main/docs/processes/breaking-changes.md) in this PR and have prepared draft pull requests for clients and consumer packages to resolve them <!-- CURSOR_SUMMARY --> --- > [!NOTE] > <sup>[Cursor Bugbot](https://cursor.com/bugbot) is generating a summary for commit 180426c. Configure [here](https://www.cursor.com/dashboard/bugbot).</sup> <!-- /CURSOR_SUMMARY -->
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Explanation
References
Checklist
Note
Low Risk
Version/changelog and dependency range updates only; no runtime logic changes in this PR.
Overview
Bumps the monorepo release version to
904.0.0and publishes@metamask/assets-controller4.1.0(changelog updated and[Unreleased]comparison link moved).Updates downstream consumers (
bridge-controllerandtransaction-pay-controller) to depend on@metamask/assets-controller@^4.1.0, with corresponding changelog entries andyarn.lockrefresh.Reviewed by Cursor Bugbot for commit fe7012e. Bugbot is set up for automated code reviews on this repo. Configure here.