Release/661.0.0

[V00D00-child]

Explanation

Release for @metamask/gator-permissions-controller (0.4.0).

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, highlighting breaking changes as necessary
• I've prepared draft pull requests for clients and consumer packages to resolve any breaking changes

---

Note

Publishes gator-permissions-controller@0.4.0 with breaking state/messenger changes and revocation APIs, and bumps signature-controller to 36.0.0 and shield-controller to 2.0.0 with updated peer deps.

• Releases:
  • @metamask/gator-permissions-controller@0.4.0 (BREAKING)
    • State now exposes pendingRevocations; add pendingRevocations getter.
    • Require messenger to allow TransactionController:* confirmation/failure/drop events.
    • Add submitRevocation and addPendingRevocation methods (and actions).
    • Add peer dependency on @metamask/transaction-controller.
  • @metamask/signature-controller@36.0.0 (BREAKING)
    • Bump peer dependency on @metamask/gator-permissions-controller to ^0.4.0.
  • @metamask/shield-controller@2.0.0 (BREAKING)
    • Bump (dev/peer) dependency on @metamask/signature-controller to ^36.0.0.
• Repo:
  • Monorepo version bump to 661.0.0.
  • Lockfile updated for new versions.

^{Written by Cursor Bugbot for commit 4476880. This will update automatically on new commits. Configure here.}

[jeffsmale90]

I left a couple nits regarding the changelog, but the changelog is sufficiently good to communicate the changes, especially given this is consumed internally only.

[mcmire]

It looks like there were new actions added to the controller messenger's allowlist (from transaction-controller). These are breaking changes and we need to include them in the changelog.

In fact it looks like transaction-controller was only added as a dev dependency. It must be added as a peer dependency as well. Can you fix this in a separate PR before merging this?

[socket-security]

No dependency changes detected. Learn more about Socket for GitHub.

👍 No dependency changes detected in pull request

[jeffsmale90]

@SocketSecurity ignore npm/@metamask/signature-controller@35.0.0

[mcmire]

Just a few more things.

[mcmire]

LGTM!

[cursor]

Bug: Peer dependency gap after signature-controller bump

The signature-controller version is being bumped to 36.0.0, but shield-controller (which has a peer dependency on signature-controller@^35.0.0) is not being updated in this release. This creates an unmet peer dependency issue because the semver range ^35.0.0 does not include version 36.0.0. The shield-controller package needs to be updated to accept signature-controller@^36.0.0 as a peer dependency to maintain compatibility across the monorepo.

 

[mcmire]

Suggested change

	- **BREAKING:** Bump `@metamask/signature-controller` from `^35.0.0` to `^36.0.0`
	- **BREAKING:** Bump peer dependency `@metamask/signature-controller` from `^35.0.0` to `^36.0.0` ([#7057](https://github.com/MetaMask/core/pull/7057))