Release 1213.0.0 - #9980
Merged
Merged
Conversation
This comment has been minimized.
This comment has been minimized.
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 0a4ed26. Configure here.
Cal-L
enabled auto-merge
August 26, 2026 21:59
tommasini
reviewed
Aug 26, 2026
tommasini
previously approved these changes
Aug 26, 2026
Cal-L
force-pushed
the
release/1213.0.0
branch
from
August 26, 2026 22:11
900be01 to
0974e7b
Compare
weitingsun
previously approved these changes
Aug 26, 2026
tommasini
previously approved these changes
Aug 26, 2026
gauthierpetetin
previously approved these changes
Aug 27, 2026
Member
|
@metamaskbot update-changelogs |
|
✅ Changelogs updated and pushed. |
metamask-ci
Bot
dismissed stale reviews from gauthierpetetin, tommasini, and weitingsun
via
August 27, 2026 08:41
f2fdd0f
weitingsun
approved these changes
Aug 27, 2026
michalconsensys
approved these changes
Aug 27, 2026
pull Bot
pushed a commit
to dmrazzy/core
that referenced
this pull request
Aug 28, 2026
## Explanation Release bridge controllers <!-- 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] > **Low Risk** > Version and changelog-only release with dependency alignment; no new runtime logic in this diff. > > **Overview** > This PR **cuts release 1214.0.0** by bumping versions and finalizing changelogs—there is no application source change in the diff. > > **`@metamask/bridge-controller` 80.1.0** documents shipped work from earlier PRs: Unified SwapBridge **quote** metrics now include sufficient-funds and normalized slippage fields ([MetaMask#9986]), and `@metamask/remote-feature-flag-controller` is bumped to `^6.1.0` ([MetaMask#9980). > > **`@metamask/bridge-status-controller` 75.4.0** documents post-submission Unified SwapBridge metrics that preserve **slippage intent** and **normalized slippage limits** ([MetaMask#9986]), and raises its dependency on `@metamask/bridge-controller` to `^80.1.0`. Root `package.json` and `yarn.lock` are updated to match. > > <sup>Reviewed by [Cursor Bugbot](https://cursor.com/bugbot) for commit 811ae77. Bugbot is set up for automated code reviews on this repo. Configure [here](https://www.cursor.com/dashboard/bugbot).</sup> <!-- /CURSOR_SUMMARY --> --------- Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
pull Bot
pushed a commit
to dmrazzy/core
that referenced
this pull request
Aug 28, 2026
## Explanation Releases `@metamask/ramps-controller` 20.0.0 to 20.1.0. No other package is being released, so the monorepo version goes 1214.0.0 to 1215.0.0. The whole branch is `yarn create-release-branch` output plus one commit from `github-actions[bot]`. Nothing was edited by hand. The bump is minor. Everything in the new section is additive except one `Fixed` entry, and nothing in it is marked `**BREAKING:**`: - **Added** `getPaymentMethodsForContext()` and the `RampsController:getPaymentMethodsForContext` messenger action, plus the `normalizeRampsAssetId()` export ([MetaMask#9801](MetaMask#9801)). - **Added** the `TERMINAL_ORDER_STATUSES` / `isTerminalOrderStatus()` exports ([MetaMask#9679](MetaMask#9679)). - **Changed** `getProviders` to preserve backend ranking metadata ([MetaMask#9955](MetaMask#9955)), and bumped `@metamask/remote-feature-flag-controller` to `^6.1.0` ([MetaMask#9945](MetaMask#9945), [MetaMask#9980](MetaMask#9980)). - **Fixed** `providerServesAsset()` / `getProvidersServingAsset()` so non-EVM CAIP-19 references are no longer lowercased when matched against a provider's `supportedCryptoCurrencies` ([MetaMask#9801](MetaMask#9801)). Solana base58 and bitcoin bech32 references are case-sensitive, so lowercasing both sides could report a provider as serving an asset it does not serve. EVM ids still match regardless of checksum casing. ### Packages deliberately left out of this release `create-release-branch` flagged four dependencies of `ramps-controller` that have unreleased changes: `@metamask/base-controller`, `@metamask/controller-utils`, `@metamask/messenger`, and `@metamask/profile-sync-controller`. All four are listed as `intentionally-skip` in the release spec. None of the PRs in this release changed `packages/ramps-controller/package.json`, so the declared ranges are untouched and the currently published versions of those four still satisfy them. ### Dependent range bump `@metamask/transaction-pay-controller` is the only in-repo consumer of `ramps-controller`. Its range moves from `^20.0.0` to `^20.1.0`, which is the tool's usual dependent-range update, and `github-actions[bot]` added the matching changelog entry. It does not need a release of its own, since `^20.0.0` already accepted 20.1.0. `yarn changelog:validate`, `yarn constraints`, and `yarn install --immutable` all pass on this branch. ## References * Releases: MetaMask#9801 (TRAM-3838), MetaMask#9679, MetaMask#9955, MetaMask#9945, MetaMask#9980 * Consumer waiting on this release: MetaMask/metamask-mobile#35346 * Related: MetaMask/metamask-mobile#34109 ## 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/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] > **Low Risk** > Version, changelog, and lockfile updates only; ramps 20.1.0 is a minor release with additive API and a targeted provider-matching fix, with no breaking changes in this cut. > > **Overview** > **Release-only PR** — no runtime code in the diff. It cuts **`@metamask/ramps-controller` `20.0.0` → `20.1.0`**, bumps the root monorepo version **`1214.0.0` → `1215.0.0`**, moves the existing `[Unreleased]` ramps changelog into **`[20.1.0]`**, and refreshes **`yarn.lock`**. > > The in-repo consumer **`@metamask/transaction-pay-controller`** gets a dependent range update **`@metamask/ramps-controller` `^20.0.0` → `^20.1.0`** plus an `[Unreleased]` changelog line; its own package version is **not** released here. > > What ships in **ramps-controller 20.1.0** (documented in the promoted changelog): **`getPaymentMethodsForContext`** / messenger action, **`normalizeRampsAssetId`**, **`TERMINAL_ORDER_STATUSES` / `isTerminalOrderStatus`**, **`getProviders` ranking metadata preservation**, dependency bump for **`remote-feature-flag-controller`**, and a **fix** so non-EVM CAIP-19 asset matching is no longer incorrectly lowercased in **`providerServesAsset` / `getProvidersServingAsset`**. > > <sup>Reviewed by [Cursor Bugbot](https://cursor.com/bugbot) for commit ec32856. Bugbot is set up for automated code reviews on this repo. Configure [here](https://www.cursor.com/dashboard/bugbot).</sup> <!-- /CURSOR_SUMMARY --> --------- Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
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
7 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
Minor release for
@metamask/remote-feature-flag-controller->6.0.0->6.1.0Minor release for
@metamask/perps-controller->13.0.0->13.1.0Also bumps dependencies
References
Checklist
Note
Low Risk
Dependency and changelog-only release with a backward-compatible optional API on feature-flag refresh; no breaking changes in this PR.
Overview
Release 1213.0.0 cuts
@metamask/remote-feature-flag-controllerat 6.1.0 (from 6.0.0) and rolls that dependency through the monorepo.The 6.1.0 release documents an optional
forceparameter onupdateRemoteFeatureFlags, so callers can refresh remote flags even when the cache has not expired (defaultfalse; still no fetch when the controller is disabled).This PR updates
package.json/yarn.lockand Unreleased changelogs for every direct consumer—e.g.assets-controller,assets-controllers,bridge-controller,config-registry-controller,core-backend,network-controller,transaction-controller,wallet,wallet-cli, and others—to depend on^6.1.0. A few packages (e.g.ramps-controller,wallet-cli) consolidate changelog lines to reflect the full bump path to 6.1.0.Reviewed by Cursor Bugbot for commit 3b2fc15. Bugbot is set up for automated code reviews on this repo. Configure here.