Release/1246.0.0 - #10152
Merged
Merged
Conversation
bergarces
had a problem deploying
to
default-branch
September 9, 2026 16:08 — with
GitHub Actions
Failure
|
❌ Failed to push changelog fixes. Check the workflow run for details. |
GuillaumeRx
approved these changes
Sep 9, 2026
Mrtenz
approved these changes
Sep 9, 2026
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
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
Minor release of assets-controllers.
References
Checklist
Note
Low Risk
Mostly semver and lockfile updates; the bundled behavior change is limited to DeFi position fetch API flags and is low blast radius outside DeFi refresh paths.
Overview
This PR cuts release 1246.0.0 and ships
@metamask/assets-controllers111.3.0, then pulls that version intoassets-controller,bridge-controller, andtransaction-pay-controller(plusyarn.lock).The new assets-controllers release is documented as a behavior tweak:
DeFiPositionsControllerV2.fetchDeFiPositionsonly sendsforceFetchDeFiPositionson the Accounts API whenforceRefreshis true, so routine fetches no longer force a backend refresh. Changelog entries record the dependency bumps; there is no new application logic in this diff beyond versioning.Reviewed by Cursor Bugbot for commit 8ea554b. Bugbot is set up for automated code reviews on this repo. Configure here.