Skip to content

Release/1001.0.0#8900

Merged
geositta merged 2 commits into
mainfrom
release/compliance-controller-2.1.0
May 27, 2026
Merged

Release/1001.0.0#8900
geositta merged 2 commits into
mainfrom
release/compliance-controller-2.1.0

Conversation

@geositta

@geositta geositta commented May 27, 2026

Copy link
Copy Markdown
Contributor

Explanation

This PR releases @metamask/compliance-controller 2.1.1.
2.1.0 release metadata was already merged to main, but that PR did not use the release PR title format, so the publish flow was not triggered and @metamask/compliance-controller@2.1.0 was not tagged or published.

Because main already contains version 2.1.0, this PR intentionally bumps the package to 2.1.1 so the release tooling can detect a package version change and publish the compliance-controller changes normally.

Relative to the last published package version, this release includes:

  • Support for configuring ComplianceService with an explicit Compliance API URL.
  • A new selectAreAnyWalletsBlocked selector.
  • Case-insensitive cached compliance lookups for valid EVM addresses.

This PR does not introduce new runtime behavior beyond the compliance-controller changes already merged to main; it corrects the release metadata so those changes can be published.

References

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
  • I've introduced breaking changes in this PR and have prepared draft pull requests for clients and consumer packages to resolve them

Note

Low Risk
Only version and changelog metadata change; compliance runtime behavior is untouched in this diff.

Overview
This PR is a release-only update for @metamask/compliance-controller: it bumps the published version from 2.1.0 to 2.1.1 in package.json and aligns CHANGELOG.md (section title, compare links, and the [Unreleased] anchor).

The only substantive changelog text change is a wording tweak under Fixed: cached wallet compliance lookups are described as matching valid EVM addresses case-insensitively (previously “EVM addresses” without “valid”). No controller, service, or test code is modified in the diff.

Reviewed by Cursor Bugbot for commit 2ae49f6. Bugbot is set up for automated code reviews on this repo. Configure here.

@geositta geositta marked this pull request as ready for review May 27, 2026 03:36
@geositta geositta requested review from a team as code owners May 27, 2026 03:36
@geositta geositta temporarily deployed to default-branch May 27, 2026 03:37 — with GitHub Actions Inactive

@cursor cursor Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Fix All in Cursor

❌ 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 2ae49f6. Configure here.

Comment thread packages/compliance-controller/package.json
@geositta geositta added this pull request to the merge queue May 27, 2026
Merged via the queue into main with commit 79379da May 27, 2026
370 checks passed
@geositta geositta deleted the release/compliance-controller-2.1.0 branch May 27, 2026 04:06
pull Bot pushed a commit to Reality2byte/core that referenced this pull request May 27, 2026
Reverts MetaMask#8900

<!-- CURSOR_SUMMARY -->
---

> [!NOTE]
> **Low Risk**
> Version and changelog-only revert with no changes to compliance logic
or published artifacts beyond semver metadata.
> 
> **Overview**
> Reverts the **`@metamask/compliance-controller`** release metadata
from **2.1.1** back to **2.1.0**, as part of undoing
**Release/1001.0.0** (revert of
[MetaMask#8900](MetaMask#8900)).
> 
> **`package.json`** sets the published version to `2.1.0` again.
**`CHANGELOG.md`** renames the unreleased section from `[2.1.1]` to
`[2.1.0]`, tweaks the fixed-entry wording for case-insensitive EVM cache
lookup, and updates compare links so `[Unreleased]` and `[2.1.0]` point
at the correct tags. No runtime or API code changes appear in this diff.
> 
> <sup>Reviewed by [Cursor Bugbot](https://cursor.com/bugbot) for commit
2a00ddf. Bugbot is set up for automated
code reviews on this repo. Configure
[here](https://www.cursor.com/dashboard/bugbot).</sup>
<!-- /CURSOR_SUMMARY -->
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants