Tags: MetaMask/core
Tags
Release/734.0.0 (#7546) ## 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/contributing.md#updating-changelogs) - [ ] 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 remote-feature-flag-controller 4.0.0 with breaking threshold flag changes and bumps Bridge/Transaction/Transaction Pay controllers to use it; monorepo version to 734.0.0. > > - **Remote Feature Flags (`packages/remote-feature-flag-controller`)** > - Release `4.0.0` with breaking changes to threshold-based flag processing: > - Persist threshold values; skip crypto for non-threshold arrays; batch cache updates; auto‑remove stale cache entries > - Update exported types (`thresholdCache`), drop `@noble/hashes`, bump `@metamask/utils` to `^11.9.0` > - **Consumers bumped to `@metamask/remote-feature-flag-controller@^4.0.0`** > - `packages/bridge-controller/package.json` > - `packages/transaction-controller/package.json` > - `packages/transaction-pay-controller/package.json` > - **Changelogs updated** > - Reflect RFFC `4.0.0` and dependency bumps across Bridge/Transaction/Transaction Pay > - **Repo metadata** > - Bump root `package.json` version to `734.0.0` > > <sup>Written by [Cursor Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit 61fca94. This will update automatically on new commits. Configure [here](https://cursor.com/dashboard?tab=bugbot).</sup> <!-- /CURSOR_SUMMARY -->
Release 733.0.0 (#7541) ## Explanation This is the release candidate for version `733.0.0`, which releases `@metamask/error-reporting-service` to add a deprecation notice. ## 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/contributing.md#updating-changelogs) - [ ] 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 `@metamask/[email protected]` (adds deprecation notice) and updates dependents; bumps monorepo to `733.0.0`. > > - **Releases**: > - `@metamask/[email protected]`: adds deprecation notice in `CHANGELOG.md` and updates package version. > - **Dependency updates**: > - Update references to `@metamask/error-reporting-service` to `^3.0.1` in `packages/eth-json-rpc-middleware/package.json`, `packages/multichain-account-service/package.json`, and `packages/network-controller/package.json`. > - **Monorepo**: > - Bump root `package.json` version to `733.0.0`. > > <sup>Written by [Cursor Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit 445b1f3. This will update automatically on new commits. Configure [here](https://cursor.com/dashboard?tab=bugbot).</sup> <!-- /CURSOR_SUMMARY -->
Release/734.0.0 (#7546) ## 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/contributing.md#updating-changelogs) - [ ] 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 remote-feature-flag-controller 4.0.0 with breaking threshold flag changes and bumps Bridge/Transaction/Transaction Pay controllers to use it; monorepo version to 734.0.0. > > - **Remote Feature Flags (`packages/remote-feature-flag-controller`)** > - Release `4.0.0` with breaking changes to threshold-based flag processing: > - Persist threshold values; skip crypto for non-threshold arrays; batch cache updates; auto‑remove stale cache entries > - Update exported types (`thresholdCache`), drop `@noble/hashes`, bump `@metamask/utils` to `^11.9.0` > - **Consumers bumped to `@metamask/remote-feature-flag-controller@^4.0.0`** > - `packages/bridge-controller/package.json` > - `packages/transaction-controller/package.json` > - `packages/transaction-pay-controller/package.json` > - **Changelogs updated** > - Reflect RFFC `4.0.0` and dependency bumps across Bridge/Transaction/Transaction Pay > - **Repo metadata** > - Bump root `package.json` version to `734.0.0` > > <sup>Written by [Cursor Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit 61fca94. This will update automatically on new commits. Configure [here](https://cursor.com/dashboard?tab=bugbot).</sup> <!-- /CURSOR_SUMMARY -->
Release 733.0.0 (#7541) ## Explanation This is the release candidate for version `733.0.0`, which releases `@metamask/error-reporting-service` to add a deprecation notice. ## 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/contributing.md#updating-changelogs) - [ ] 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 `@metamask/[email protected]` (adds deprecation notice) and updates dependents; bumps monorepo to `733.0.0`. > > - **Releases**: > - `@metamask/[email protected]`: adds deprecation notice in `CHANGELOG.md` and updates package version. > - **Dependency updates**: > - Update references to `@metamask/error-reporting-service` to `^3.0.1` in `packages/eth-json-rpc-middleware/package.json`, `packages/multichain-account-service/package.json`, and `packages/network-controller/package.json`. > - **Monorepo**: > - Bump root `package.json` version to `733.0.0`. > > <sup>Written by [Cursor Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit 445b1f3. This will update automatically on new commits. Configure [here](https://cursor.com/dashboard?tab=bugbot).</sup> <!-- /CURSOR_SUMMARY -->
Release 732.0.0 (#7534) <!-- CURSOR_SUMMARY --> > [!NOTE] > Cuts release 732.0.0, upgrading @metamask/controller-utils to 11.17.0 and @metamask/network-controller to 27.1.0 (adds MegaETH Testnet v2), and propagates these across packages. > > - **Release** > - Bump monorepo version to `732.0.0`. > - **Dependencies** > - Upgrade `@metamask/controller-utils` to `^11.17.0` across controllers/services. > - Upgrade `@metamask/network-controller` to `^27.1.0` across packages (and related dev deps). > - **Network Controller (`@metamask/[email protected]`)** > - Adds MegaETH Testnet v2 as default custom network; fixes EIP-1559 metadata update; bumps `controller-utils`. > - **Changelogs** > - Update entries to reflect the above bumps and expand previous "peer → direct deps" notes to include this release. > > <sup>Written by [Cursor Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit b0ad5bc. This will update automatically on new commits. Configure [here](https://cursor.com/dashboard?tab=bugbot).</sup> <!-- /CURSOR_SUMMARY --> --------- Co-authored-by: cryptodev-2s <[email protected]>
Release/731.0.0 (#7531) ## Explanation some ramps-controller variable name changes and other small fixes are needed for the initial integration of the ramps PR in the mobile codebase: MetaMask/metamask-mobile#24044 <!-- 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/contributing.md#updating-changelogs) - [ ] 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] > Release 731.0.0, promoting ramps-controller to 2.0.0 with breaking renames and a geolocation fix. > > - **Ramps Controller (`@metamask/ramps-controller` 2.0.0)**: > - **BREAKING:** Rename `OnRampService` → `RampsService` and `OnRampEnvironment` → `RampsEnvironment`. > - **BREAKING:** Rename action types from `OnRampService:*` → `RampsService:*` (e.g., `getGeolocation`). > - Fix `RampsService#getGeolocation` to parse response text within policy execution. > - **Repo**: > - Bump monorepo version to `731.0.0`. > - Update changelog links for new ramps-controller release. > > <sup>Written by [Cursor Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit 1f7402f. This will update automatically on new commits. Configure [here](https://cursor.com/dashboard?tab=bugbot).</sup> <!-- /CURSOR_SUMMARY -->
Release 730.0.0 (#7529) ## Explanation - initial analytics-controller release 1.0.0 <!-- 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/contributing.md#updating-changelogs) - [ ] 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] > Bumps monorepo to 730.0.0 and publishes @metamask/analytics-controller 1.0.0 with updated changelog links. > > - **Release** > - Bump monorepo `package.json` version to `730.0.0`. > - **@metamask/analytics-controller** > - Set package version to `1.0.0` (initial release). > - Update `CHANGELOG.md` with `1.0.0` section and compare/release links. > > <sup>Written by [Cursor Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit de04140. This will update automatically on new commits. Configure [here](https://cursor.com/dashboard?tab=bugbot).</sup> <!-- /CURSOR_SUMMARY -->
Release/729.0.0 (#7524) ## 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? --> Patch release of `@metamask/claims-controller` (`v0.3.1`) ## 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] > Publish `@metamask/claims-controller` v0.3.1 (adds `updatedAt` to claim drafts) and bump monorepo to 729.0.0. > > - **Packages**: > - `@metamask/[email protected]` > - Add `updatedAt` field to claim drafts; update changelog compare links. > - **Monorepo**: > - Bump root version to `729.0.0`. > > <sup>Written by [Cursor Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit 5a13997. This will update automatically on new commits. Configure [here](https://cursor.com/dashboard?tab=bugbot).</sup> <!-- /CURSOR_SUMMARY -->
Release/728.0.0 (#7519) ## Explanation This PR upgrades `@metamask/remote-feature-flag-controller` from v3.0.0 to v3.1.0 across the monorepo and bumps the monorepo version to 728.0.0. ### Current State The `@metamask/remote-feature-flag-controller` package is currently at version 3.0.0, which supports version-gated feature flags but lacks the ability for clients to locally override feature flag values for testing, debugging, or development purposes. ### Solution Version 3.1.0 introduces new override functionality that allows clients to set local overrides for feature flags. These overrides take precedence over remote feature flags, enabling: - Local testing of feature flags without modifying remote configuration - Debugging specific flag combinations - Development workflows that require flag manipulation ### Changes in v4.0.0 **New APIs:** - `setFlagOverride(flagName, value)` - Set a local override for a specific feature flag - `removeFlagOverride(flagName)` - Clear the local override for a specific feature flag - `clearAllFlagOverrides()` - Clear all local feature flag overrides **New Optional State Properties:** - `localOverrides` - Local overrides for feature flags that take precedence over remote flags - `rawRemoteFeatureFlags` - Raw flag value for all feature flags (separate from the merged view) **New Exports:** - `RemoteFeatureFlagControllerSetFlagOverrideAction` - `RemoteFeatureFlagControllerRemoveFlagOverrideAction` - `RemoteFeatureFlagControllerClearAllFlagOverridesAction` ### Breaking Changes While this release is primarily additive, it's marked as a major version bump (v3.1.0) because: 1. New state properties (`localOverrides`, `rawRemoteFeatureFlags`) are added to the controller state, which affects state serialization/deserialization 2. Consumers need to ensure their state migration handles these new properties 3. Type definitions have been updated to include the new action types ### Package Updates The following packages have been updated to use `@metamask/remote-feature-flag-controller@^3.1.0`: - `@metamask/bridge-controller` - `@metamask/transaction-controller` - `@metamask/transaction-pay-controller` All changelogs have been updated to document this breaking dependency upgrade. ## References - Related to [#7271](#7271) - Add override functionality to remote feature flags - Related to [#7519](#7519) - Upgrade remote-feature-flag-controller to v3.1.0 ## 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) - [ ] 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] > Bumps the monorepo to 728.0.0 and upgrades `@metamask/remote-feature-flag-controller` to 3.1.0 with flag override APIs, updating dependent packages and changelogs. > > - **Versioning** > - Bump monorepo `version` to `728.0.0`. > - **Packages** > - **`packages/remote-feature-flag-controller`** > - Release `3.1.0`; adds local flag override APIs (`setFlagOverride`, `removeFlagOverride`, `clearAllFlagOverrides`) and optional state/exports; update `CHANGELOG.md`. > - **Dependents** > - Update dependencies to `@metamask/remote-feature-flag-controller@^3.1.0` in `packages/bridge-controller`, `packages/transaction-controller`, and `packages/transaction-pay-controller`. > - Reflect dependency bump in respective `CHANGELOG.md` files. > - **Tooling** > - Update `yarn.lock` to resolve new dependency versions. > > <sup>Written by [Cursor Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit 53e3b53. This will update automatically on new commits. Configure [here](https://cursor.com/dashboard?tab=bugbot).</sup> <!-- /CURSOR_SUMMARY -->
Release/728.0.0 (#7519) ## Explanation This PR upgrades `@metamask/remote-feature-flag-controller` from v3.0.0 to v3.1.0 across the monorepo and bumps the monorepo version to 728.0.0. ### Current State The `@metamask/remote-feature-flag-controller` package is currently at version 3.0.0, which supports version-gated feature flags but lacks the ability for clients to locally override feature flag values for testing, debugging, or development purposes. ### Solution Version 3.1.0 introduces new override functionality that allows clients to set local overrides for feature flags. These overrides take precedence over remote feature flags, enabling: - Local testing of feature flags without modifying remote configuration - Debugging specific flag combinations - Development workflows that require flag manipulation ### Changes in v4.0.0 **New APIs:** - `setFlagOverride(flagName, value)` - Set a local override for a specific feature flag - `removeFlagOverride(flagName)` - Clear the local override for a specific feature flag - `clearAllFlagOverrides()` - Clear all local feature flag overrides **New Optional State Properties:** - `localOverrides` - Local overrides for feature flags that take precedence over remote flags - `rawRemoteFeatureFlags` - Raw flag value for all feature flags (separate from the merged view) **New Exports:** - `RemoteFeatureFlagControllerSetFlagOverrideAction` - `RemoteFeatureFlagControllerRemoveFlagOverrideAction` - `RemoteFeatureFlagControllerClearAllFlagOverridesAction` ### Breaking Changes While this release is primarily additive, it's marked as a major version bump (v3.1.0) because: 1. New state properties (`localOverrides`, `rawRemoteFeatureFlags`) are added to the controller state, which affects state serialization/deserialization 2. Consumers need to ensure their state migration handles these new properties 3. Type definitions have been updated to include the new action types ### Package Updates The following packages have been updated to use `@metamask/remote-feature-flag-controller@^3.1.0`: - `@metamask/bridge-controller` - `@metamask/transaction-controller` - `@metamask/transaction-pay-controller` All changelogs have been updated to document this breaking dependency upgrade. ## References - Related to [#7271](#7271) - Add override functionality to remote feature flags - Related to [#7519](#7519) - Upgrade remote-feature-flag-controller to v3.1.0 ## 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) - [ ] 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] > Bumps the monorepo to 728.0.0 and upgrades `@metamask/remote-feature-flag-controller` to 3.1.0 with flag override APIs, updating dependent packages and changelogs. > > - **Versioning** > - Bump monorepo `version` to `728.0.0`. > - **Packages** > - **`packages/remote-feature-flag-controller`** > - Release `3.1.0`; adds local flag override APIs (`setFlagOverride`, `removeFlagOverride`, `clearAllFlagOverrides`) and optional state/exports; update `CHANGELOG.md`. > - **Dependents** > - Update dependencies to `@metamask/remote-feature-flag-controller@^3.1.0` in `packages/bridge-controller`, `packages/transaction-controller`, and `packages/transaction-pay-controller`. > - Reflect dependency bump in respective `CHANGELOG.md` files. > - **Tooling** > - Update `yarn.lock` to resolve new dependency versions. > > <sup>Written by [Cursor Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit 53e3b53. This will update automatically on new commits. Configure [here](https://cursor.com/dashboard?tab=bugbot).</sup> <!-- /CURSOR_SUMMARY -->
PreviousNext