Tags: MetaMask/core
Tags
Release/1272.0.0 (#10350) ## Explanation Releasing @metamask/transaction-pay-controller ## References Related to https://consensyssoftware.atlassian.net/browse/CONF-2063 ## 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
Release 1271.0.0 (#10348) ## 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 - [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] > **Medium Risk** > Release-only diff, but it rolls out profile-sync MFA/step-up and credential enrollment to many auth-adjacent controllers; consumers should verify messenger wiring and elevated-token flows when upgrading. > > **Overview** > This PR cuts **Release 1271.0.0** by bumping the root monorepo version and publishing **`@metamask/profile-sync-controller` `32.2.0`** (from `32.1.1`), with the `32.2.0` changelog section finalized and compare links updated. > > It **propagates `^32.2.0`** across dependents (account-tree, assets, bridge, bridge-status, claims, core-backend, kyc, notification-services, perps devDep, profile-metrics, ramps, shield, smart-transactions, social, subscription, and others) and records the bump in each package’s **Unreleased** changelog. **`yarn.lock`** is refreshed accordingly. > > What ships in **`32.2.0`** (already merged; this PR only releases it): MFA/step-up on `AuthenticationController` (`beginStepUp` / `completeStepUp`, in-memory elevated token), credential enrollment APIs, passkey/email OTP SDK helpers, `MfaError` types, and **`rampsOrders`** user-storage feature name. > > <sup>Reviewed by [Cursor Bugbot](https://cursor.com/bugbot) for commit 9c0109c. 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>
Release/1270.0.0 (#10341) ## 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] > **Low Risk** > Version and dependency metadata only; consumers pick up bridge-controller 81.3.0 behavior from the prior feature work, not new logic in this PR. > > **Overview** > This is a **release cut** with no runtime source changes in the diff. It bumps the root monorepo from **1269.0.0** to **1270.0.0**, publishes **`@metamask/bridge-controller` 81.3.0**, and records that release in its changelog (including the already-landed optional **`quote.feeData.reserve`** on V2 quotes for native minimum-balance requirements). > > **`@metamask/bridge-status-controller`** is updated to depend on **`@metamask/bridge-controller` ^81.3.0** (was ^81.2.0), with a matching Unreleased changelog note and **`yarn.lock`** refresh. > > <sup>Reviewed by [Cursor Bugbot](https://cursor.com/bugbot) for commit 86a52bd. 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>
Release 1269.0.0 (#10338) ## Summary - Bump `@metamask/core-monorepo` to `1269.0.0` - Bump `@metamask/perps-controller` to `17.3.0` - Fixed: use Lighter's reported executed amount for order filled sizes so canceled orders do not appear fully filled (#10308) ## Test plan - [x] `yarn changelog:validate` - [ ] CI 🤖 Generated with [Claude Code](https://claude.com/claude-code) <!-- CURSOR_SUMMARY --> --- > [!NOTE] > **Low Risk** > Version and changelog updates only; trading behavior change was already merged in the referenced fix PR. > > **Overview** > This is a **release-only** PR: it bumps the monorepo to **`1269.0.0`** and publishes **`@metamask/perps-controller` `17.3.0`**, with matching **`CHANGELOG.md`** and compare-link updates. > > The **`17.3.0`** notes document the shipped fix from [#10308](#10308): **Lighter order filled sizes now use the venue’s reported executed amount**, so partially filled then **canceled** orders no longer show as **100% filled** in UI/state. > > There are **no runtime code changes** in this diff—only version metadata and release notes. > > <sup>Reviewed by [Cursor Bugbot](https://cursor.com/bugbot) for commit ea73c3b. Bugbot is set up for automated code reviews on this repo. Configure [here](https://www.cursor.com/dashboard/bugbot).</sup> <!-- /CURSOR_SUMMARY -->
Release/1272.0.0 (#10350) ## Explanation Releasing @metamask/transaction-pay-controller ## References Related to https://consensyssoftware.atlassian.net/browse/CONF-2063 ## 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
Release 1271.0.0 (#10348) ## 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 - [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] > **Medium Risk** > Release-only diff, but it rolls out profile-sync MFA/step-up and credential enrollment to many auth-adjacent controllers; consumers should verify messenger wiring and elevated-token flows when upgrading. > > **Overview** > This PR cuts **Release 1271.0.0** by bumping the root monorepo version and publishing **`@metamask/profile-sync-controller` `32.2.0`** (from `32.1.1`), with the `32.2.0` changelog section finalized and compare links updated. > > It **propagates `^32.2.0`** across dependents (account-tree, assets, bridge, bridge-status, claims, core-backend, kyc, notification-services, perps devDep, profile-metrics, ramps, shield, smart-transactions, social, subscription, and others) and records the bump in each package’s **Unreleased** changelog. **`yarn.lock`** is refreshed accordingly. > > What ships in **`32.2.0`** (already merged; this PR only releases it): MFA/step-up on `AuthenticationController` (`beginStepUp` / `completeStepUp`, in-memory elevated token), credential enrollment APIs, passkey/email OTP SDK helpers, `MfaError` types, and **`rampsOrders`** user-storage feature name. > > <sup>Reviewed by [Cursor Bugbot](https://cursor.com/bugbot) for commit 9c0109c. 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>
Release 1269.0.0 (#10338) ## Summary - Bump `@metamask/core-monorepo` to `1269.0.0` - Bump `@metamask/perps-controller` to `17.3.0` - Fixed: use Lighter's reported executed amount for order filled sizes so canceled orders do not appear fully filled (#10308) ## Test plan - [x] `yarn changelog:validate` - [ ] CI 🤖 Generated with [Claude Code](https://claude.com/claude-code) <!-- CURSOR_SUMMARY --> --- > [!NOTE] > **Low Risk** > Version and changelog updates only; trading behavior change was already merged in the referenced fix PR. > > **Overview** > This is a **release-only** PR: it bumps the monorepo to **`1269.0.0`** and publishes **`@metamask/perps-controller` `17.3.0`**, with matching **`CHANGELOG.md`** and compare-link updates. > > The **`17.3.0`** notes document the shipped fix from [#10308](#10308): **Lighter order filled sizes now use the venue’s reported executed amount**, so partially filled then **canceled** orders no longer show as **100% filled** in UI/state. > > There are **no runtime code changes** in this diff—only version metadata and release notes. > > <sup>Reviewed by [Cursor Bugbot](https://cursor.com/bugbot) for commit ea73c3b. Bugbot is set up for automated code reviews on this repo. Configure [here](https://www.cursor.com/dashboard/bugbot).</sup> <!-- /CURSOR_SUMMARY -->
Release/1270.0.0 (#10341) ## 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] > **Low Risk** > Version and dependency metadata only; consumers pick up bridge-controller 81.3.0 behavior from the prior feature work, not new logic in this PR. > > **Overview** > This is a **release cut** with no runtime source changes in the diff. It bumps the root monorepo from **1269.0.0** to **1270.0.0**, publishes **`@metamask/bridge-controller` 81.3.0**, and records that release in its changelog (including the already-landed optional **`quote.feeData.reserve`** on V2 quotes for native minimum-balance requirements). > > **`@metamask/bridge-status-controller`** is updated to depend on **`@metamask/bridge-controller` ^81.3.0** (was ^81.2.0), with a matching Unreleased changelog note and **`yarn.lock`** refresh. > > <sup>Reviewed by [Cursor Bugbot](https://cursor.com/bugbot) for commit 86a52bd. 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>
Release/1268.0.0 (#10326) ## Explanation Cut `@metamask/ramps-controller@24.0.0` so Mobile can consume VBA onboarding hydration from #10278, plus a required patch of `@metamask/transaction-pay-controller@29.0.1` because it is a workspace dependent of that major bump. Ramps is a **major** because hosts must wire four new `KycController` messenger actions on `RampsControllerMessenger`. ## References - Core feature: #10278 - Mobile consumer (draft): MetaMask/metamask-mobile#36522 ## 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) - [x] 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 ## Test plan - [ ] Changelog for `@metamask/ramps-controller` 24.0.0 looks correct (no Uncategorized) - [ ] Changelog for `@metamask/transaction-pay-controller` 29.0.1 looks correct (no Uncategorized) - [ ] Published packages: ramps-controller `23.0.0` → `24.0.0`, transaction-pay-controller `29.0.0` → `29.0.1` - [ ] After merge, confirm GitHub release tags and npm publish of both packages <!-- CURSOR_SUMMARY --> --- > [!NOTE] > **Medium Risk** > The major ramps release forces client messenger wiring for KYC hydration; this PR only cuts versions but downstream apps must upgrade integrations before adopting 24.0.0. > > **Overview** > Release **1268.0.0** publishes **`@metamask/ramps-controller@24.0.0`**, packaging the VBA onboarding and NeoBank autoramp work from #10278 that was previously under `[Unreleased]`. The changelog section is finalized (including a minor formatting fix on an older breaking-change bullet), and compare links are updated for the new tag. > > The ramps bump is a **major** because consumers must delegate four **`KycController`** messenger actions on **`RampsControllerMessenger`** for VBA onboarding hydration (along with the other 24.0.0 API additions already documented there). > > **`@metamask/transaction-pay-controller`** is patched to **`29.0.1`** so its dependency moves from **`@metamask/ramps-controller@^23.0.0`** to **`^24.0.0`**, with matching **`package.json`**, changelog, and **`yarn.lock`** updates. No application logic changes appear in this diff—only versioning and release metadata. > > <sup>Reviewed by [Cursor Bugbot](https://cursor.com/bugbot) for commit 20f97cc. 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> Co-authored-by: Amitabh Aggarwal <aggarwal.amitabh@gmail.com> Co-authored-by: Cursor <cursoragent@cursor.com>
Release/1267.0.0 (#10313) ## Explanation Releases a new version of Social controller. ## 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** > Only version and changelog edits; no runtime or API code changes in this diff. > > **Overview** > This is a **release cut** for the core monorepo and `@metamask/social-controllers`, not a feature PR in the diff itself. > > It bumps the root monorepo version **1266.0.0 → 1267.0.0** and publishes **`@metamask/social-controllers` 3.0.1 → 3.0.2**. The social-controllers **CHANGELOG** is updated with a new **[3.0.2]** section (and compare links), documenting work already merged: optional **`rankingTag`** on **`TraderProfileResponse`**, a **`@metamask/profile-sync-controller`** dependency bump, and a **`lint:tsc`** / CI housekeeping note. > > <sup>Reviewed by [Cursor Bugbot](https://cursor.com/bugbot) for commit 27735db. Bugbot is set up for automated code reviews on this repo. Configure [here](https://www.cursor.com/dashboard/bugbot).</sup> <!-- /CURSOR_SUMMARY -->
PreviousNext