Merged
Conversation
cryptodev-2s
requested changes
Apr 2, 2026
Co-authored-by: cryptodev-2s <109512101+cryptodev-2s@users.noreply.github.com>
Co-authored-by: cryptodev-2s <109512101+cryptodev-2s@users.noreply.github.com>
cryptodev-2s
approved these changes
Apr 2, 2026
micaelae
pushed a commit
that referenced
this pull request
Apr 7, 2026
## Explanation This release bumps `@metamask/compliance-controller` from `1.0.2` to `2.0.0`. The major version bump is required due to breaking changes in the compliance controller — see the [changelog](https://github.com/MetaMask/core/blob/release/900.0.0/packages/compliance-controller/CHANGELOG.md) for full details. ### Packages released | Package | From | To | Type | |---|---|---|---| | `@metamask/compliance-controller` | `1.0.2` | `2.0.0` | major | ### Summary of changes **Added** - `generate-action-types` CLI tool available as a subpath export via the `@metamask/messenger` bump ([#8264](#8264)) **Breaking changes** - Removed proactive bulk-fetch pattern from `ComplianceController` and `ComplianceService` ([#8365](#8365)) - `state.blockedWallets` and `state.blockedWalletsLastFetched` removed — consumers with persisted state must drop these fields on migration - `init()`, `updateBlockedWallets()` controller methods removed - `blockedWalletsRefreshInterval` constructor option removed - `ComplianceControllerInitAction`, `ComplianceControllerUpdateBlockedWalletsAction`, `ComplianceServiceUpdateBlockedWalletsAction`, `BlockedWalletsInfo` removed from public API - `checkWalletCompliance` / `checkWalletsCompliance` now fall back to the per-address cache on API failure - `selectIsWalletBlocked` now reads solely from `walletComplianceStatusMap` ## References - [#8365](#8365) — refactor(compliance): remove initial block wallets call ## 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 - [x] I've introduced breaking changes in this PR and have prepared draft pull requests for clients and consumer packages to resolve them <!-- CURSOR_SUMMARY --> --- > [!NOTE] > **Medium Risk** > Release-only changes, but it publishes a new major `@metamask/compliance-controller` version with breaking API/state removals that downstream consumers must migrate to. > > **Overview** > Bumps the monorepo version to `900.0.0` and releases `@metamask/compliance-controller` `2.0.0`. > > Updates the compliance-controller changelog to document the **breaking** removal of the blocked-wallets bulk-fetch flow and related public API/state fields, and adjusts the `[Unreleased]`/`[2.0.0]` compare links accordingly. > > <sup>Written by [Cursor Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit 7060084. This will update automatically on new commits. Configure [here](https://cursor.com/dashboard?tab=bugbot).</sup> <!-- /CURSOR_SUMMARY --> --------- Co-authored-by: cryptodev-2s <109512101+cryptodev-2s@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
2 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
This release bumps
@metamask/compliance-controllerfrom1.0.2to2.0.0.The major version bump is required due to breaking changes in the compliance controller — see the changelog for full details.
Packages released
@metamask/compliance-controller1.0.22.0.0Summary of changes
Added
generate-action-typesCLI tool available as a subpath export via the@metamask/messengerbump (#8264)Breaking changes
ComplianceControllerandComplianceService(#8365)state.blockedWalletsandstate.blockedWalletsLastFetchedremoved — consumers with persisted state must drop these fields on migrationinit(),updateBlockedWallets()controller methods removedblockedWalletsRefreshIntervalconstructor option removedComplianceControllerInitAction,ComplianceControllerUpdateBlockedWalletsAction,ComplianceServiceUpdateBlockedWalletsAction,BlockedWalletsInforemoved from public APIcheckWalletCompliance/checkWalletsCompliancenow fall back to the per-address cache on API failureselectIsWalletBlockednow reads solely fromwalletComplianceStatusMapReferences
Checklist
Note
Medium Risk
Release-only changes, but it publishes a new major
@metamask/compliance-controllerversion with breaking API/state removals that downstream consumers must migrate to.Overview
Bumps the monorepo version to
900.0.0and releases@metamask/compliance-controller2.0.0.Updates the compliance-controller changelog to document the breaking removal of the blocked-wallets bulk-fetch flow and related public API/state fields, and adjusts the
[Unreleased]/[2.0.0]compare links accordingly.Written by Cursor Bugbot for commit 7060084. This will update automatically on new commits. Configure here.