Skip to content

Comments

Release/751.0.0#7634

Merged
V00D00-child merged 11 commits intomainfrom
release/751.0.0
Jan 15, 2026
Merged

Release/751.0.0#7634
V00D00-child merged 11 commits intomainfrom
release/751.0.0

Conversation

@MoMannn
Copy link
Contributor

@MoMannn MoMannn commented Jan 15, 2026

Explanation

Releases:

  • @metamask/gator-permissions-controller@1.0.0
  • @metamask/eth-json-rpc-middleware@23.0.0
  • @metamask/signature-controller@38.1.0

Both gator-permissions-controller and eth-json-rpc-middleware produce breaking changes to align with latest eip 7715 specs.

References

Required by: MetaMask/metamask-extension#39176

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

Releases coordinated majors with EIP‑7715 updates and dependency alignments.

  • BREAKING: @metamask/eth-json-rpc-middleware@23.0.0 updates wallet_requestExecutionPermissions to 7715 spec; adds wallet_getSupportedExecutionPermissions and wallet_getGrantedExecutionPermissions
  • BREAKING: @metamask/gator-permissions-controller@1.0.0 updates core types to 7715 revisions
  • BREAKING: @metamask/shield-controller@5.0.0 now depends on @metamask/signature-controller@39.0.0; decodedPermission shape in signature requests changes
  • @metamask/signature-controller@39.0.0 bumps to use gator-permissions-controller@1.0.0
  • @metamask/network-controller bumps dependency to eth-json-rpc-middleware@^23.0.0 and updates changelog (notes new ConnectivityController:getState requirement)
  • Bumps monorepo version to 751.0.0 and updates lockfile

Written by Cursor Bugbot for commit e0a1409. This will update automatically on new commits. Configure here.

@MoMannn MoMannn requested review from a team as code owners January 15, 2026 07:42
@MoMannn MoMannn requested a review from cryptodev-2s January 15, 2026 08:15
V00D00-child
V00D00-child previously approved these changes Jan 15, 2026
mcmire
mcmire previously approved these changes Jan 15, 2026
Copy link
Contributor

@mcmire mcmire left a comment

Choose a reason for hiding this comment

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

network-controller changes look good.

I've also looked at the impact of the DecodedPermission changes in SignatureController and there don't seem to be breaking changes there. Oh never mind, I see Mark's comments now.

@MoMannn MoMannn dismissed stale reviews from mcmire and V00D00-child via 65ceb20 January 15, 2026 15:25
@MoMannn
Copy link
Contributor Author

MoMannn commented Jan 15, 2026

network-controller changes look good.

I've also looked at the impact of the DecodedPermission changes in SignatureController and there don't seem to be breaking changes there.

as per @Gudahtt Review we still decided to bump SignatureController as a major release.

@MoMannn MoMannn requested a review from mcmire January 15, 2026 15:52
V00D00-child
V00D00-child previously approved these changes Jan 15, 2026
cryptodev-2s
cryptodev-2s previously approved these changes Jan 15, 2026
Copy link
Contributor

@cryptodev-2s cryptodev-2s left a comment

Choose a reason for hiding this comment

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

LGTM!

Copy link
Contributor

@cryptodev-2s cryptodev-2s left a comment

Choose a reason for hiding this comment

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

LGTM!

@V00D00-child V00D00-child added this pull request to the merge queue Jan 15, 2026
Merged via the queue into main with commit 9749c4b Jan 15, 2026
300 of 306 checks passed
@V00D00-child V00D00-child deleted the release/751.0.0 branch January 15, 2026 17:27
github-merge-queue bot pushed a commit to MetaMask/metamask-extension that referenced this pull request Jan 21, 2026
## **Description**

This PR updates the codebase to align with API changes in the
`@metamask/gator-permissions-controller` package.

**Reason for the change:**
The upstream `@metamask/gator-permissions-controller` package has
updated its type definitions and data structures. This PR ensures
compatibility with those changes.

**Changes included:**

1. **Type simplification**: Removed the `Signer` generic parameter from
`StoredGatorPermissionSanitized<Signer, PermissionTypesWithCustom>` →
`StoredGatorPermissionSanitized<PermissionTypesWithCustom>` across all
files (selectors, hooks, components, and tests).

2. **Data structure updates**:
- `permissionResponse.address` → `permissionResponse.from` (delegator
address)
- `decodedPermission.signer.data.address` → `decodedPermission.to`
(delegate/recipient address)
- `permissionResponse.signerMeta.delegationManager` →
`permissionResponse.delegationManager` (flattened structure)
- `permission.rules` → `permissionResponse.rules` (rules array location
change)

3. **New RPC methods**: Added support for two new unrestricted methods:
- `wallet_getSupportedExecutionPermissions` - Returns supported
permission types (filtered by enabled advanced permissions)
- `wallet_getGrantedExecutionPermissions` - Returns granted execution
permissions

[![Open in GitHub
Codespaces](https://github.com/codespaces/badge.svg)](https://codespaces.new/MetaMask/metamask-extension/pull/39176?quickstart=1)
## **Changelog**

<!--
If this PR is not End-User-Facing and should not show up in the
CHANGELOG, you can choose to either:
1. Write `CHANGELOG entry: null`
2. Label with `no-changelog`

If this PR is End-User-Facing, please write a short User-Facing
description in the past tense like:
`CHANGELOG entry: Added a new tab for users to see their NFTs`
`CHANGELOG entry: Fixed a bug that was causing some NFTs to flicker`

(This helps the Release Engineer do their job more quickly and
accurately)
-->

CHANGELOG entry: Added support for
`wallet_getSupportedExecutionPermissions` and
`wallet_getGrantedExecutionPermissions` RPC methods.
CHANGELOG entry: Updated to latest 7715 standart.

## **Related issues**

Depends on: MetaMask/core#7603
Relates to: MetaMask/snap-7715-permissions#249
Requires: MetaMask/core#7634
Requires: MetaMask/snap-7715-permissions#254

## **Manual testing steps**

For manual testing check:
MetaMask/snap-7715-permissions#249

## **Pre-merge author checklist**

- [x] I've followed [MetaMask Contributor
Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask
Extension Coding
Standards](https://github.com/MetaMask/metamask-extension/blob/main/.github/guidelines/CODING_GUIDELINES.md).
- [x] I've completed the PR template to the best of my ability
- [x] I’ve included tests if applicable
- [x] I’ve documented my code using [JSDoc](https://jsdoc.app/) format
if applicable
- [x] I’ve applied the right labels on the PR (see [labeling
guidelines](https://github.com/MetaMask/metamask-extension/blob/main/.github/guidelines/LABELING_GUIDELINES.md)).
Not required for external contributors.

## **Pre-merge reviewer checklist**

- [ ] I've manually tested the PR (e.g. pull and build branch, run the
app, test code being changed).
- [ ] I confirm that this PR addresses all acceptance criteria described
in the ticket it closes and includes the necessary testing evidence such
as recordings and or screenshots.

<!-- CURSOR_SUMMARY -->
---

> [!NOTE]
> Updates codebase to the 7715/gator-permissions v1 API and introduces
execution-permissions query RPCs.
> 
> - Refactors to `@metamask/gator-permissions-controller@^1.0.0`: remove
`Signer` generic, move `permission.rules` to `permissionResponse.rules`,
rename `permissionResponse.address`→`from`,
`signerMeta.delegationManager`→`delegationManager`, and decoded
permission `signer...address`→`to`; applies across hooks, selectors,
components, and tests
> - Adds `wallet_getSupportedExecutionPermissions` (filters by enabled
advanced types) and `wallet_getGrantedExecutionPermissions`; wires
through `createMetamaskMiddleware` and forwards to the permissions
kernel snap
> - Bumps related deps (`eth-json-rpc-middleware@^23`,
`permissions-kernel-snap@^1.0.0`, `signature-controller@^39`,
`shield-controller@^5`, etc.) and adjusts LavaMoat policies to use the
updated middleware pathing
> - Updates PPOM/confirmation tests and stories to the new permission
shape; no functional changes beyond API alignment
> 
> <sup>Written by [Cursor
Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit
a522169. This will update automatically
on new commits. Configure
[here](https://cursor.com/dashboard?tab=bugbot).</sup>
<!-- /CURSOR_SUMMARY -->

---------

Co-authored-by: MetaMask Bot <metamaskbot@users.noreply.github.com>
github-merge-queue bot pushed a commit to MetaMask/metamask-extension that referenced this pull request Jan 21, 2026
## **Description**

This PR updates the codebase to align with API changes in the
`@metamask/gator-permissions-controller` package.

**Reason for the change:**
The upstream `@metamask/gator-permissions-controller` package has
updated its type definitions and data structures. This PR ensures
compatibility with those changes.

**Changes included:**

1. **Type simplification**: Removed the `Signer` generic parameter from
`StoredGatorPermissionSanitized<Signer, PermissionTypesWithCustom>` →
`StoredGatorPermissionSanitized<PermissionTypesWithCustom>` across all
files (selectors, hooks, components, and tests).

2. **Data structure updates**:
- `permissionResponse.address` → `permissionResponse.from` (delegator
address)
- `decodedPermission.signer.data.address` → `decodedPermission.to`
(delegate/recipient address)
- `permissionResponse.signerMeta.delegationManager` →
`permissionResponse.delegationManager` (flattened structure)
- `permission.rules` → `permissionResponse.rules` (rules array location
change)

3. **New RPC methods**: Added support for two new unrestricted methods:
- `wallet_getSupportedExecutionPermissions` - Returns supported
permission types (filtered by enabled advanced permissions)
- `wallet_getGrantedExecutionPermissions` - Returns granted execution
permissions

[![Open in GitHub
Codespaces](https://github.com/codespaces/badge.svg)](https://codespaces.new/MetaMask/metamask-extension/pull/39176?quickstart=1)
## **Changelog**

<!--
If this PR is not End-User-Facing and should not show up in the
CHANGELOG, you can choose to either:
1. Write `CHANGELOG entry: null`
2. Label with `no-changelog`

If this PR is End-User-Facing, please write a short User-Facing
description in the past tense like:
`CHANGELOG entry: Added a new tab for users to see their NFTs`
`CHANGELOG entry: Fixed a bug that was causing some NFTs to flicker`

(This helps the Release Engineer do their job more quickly and
accurately)
-->

CHANGELOG entry: Added support for
`wallet_getSupportedExecutionPermissions` and
`wallet_getGrantedExecutionPermissions` RPC methods.
CHANGELOG entry: Updated to latest 7715 standart.

## **Related issues**

Depends on: MetaMask/core#7603
Relates to: MetaMask/snap-7715-permissions#249
Requires: MetaMask/core#7634
Requires: MetaMask/snap-7715-permissions#254

## **Manual testing steps**

For manual testing check:
MetaMask/snap-7715-permissions#249

## **Pre-merge author checklist**

- [x] I've followed [MetaMask Contributor
Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask
Extension Coding
Standards](https://github.com/MetaMask/metamask-extension/blob/main/.github/guidelines/CODING_GUIDELINES.md).
- [x] I've completed the PR template to the best of my ability
- [x] I’ve included tests if applicable
- [x] I’ve documented my code using [JSDoc](https://jsdoc.app/) format
if applicable
- [x] I’ve applied the right labels on the PR (see [labeling
guidelines](https://github.com/MetaMask/metamask-extension/blob/main/.github/guidelines/LABELING_GUIDELINES.md)).
Not required for external contributors.

## **Pre-merge reviewer checklist**

- [ ] I've manually tested the PR (e.g. pull and build branch, run the
app, test code being changed).
- [ ] I confirm that this PR addresses all acceptance criteria described
in the ticket it closes and includes the necessary testing evidence such
as recordings and or screenshots.

<!-- CURSOR_SUMMARY -->
---

> [!NOTE]
> Updates codebase to the 7715/gator-permissions v1 API and introduces
execution-permissions query RPCs.
> 
> - Refactors to `@metamask/gator-permissions-controller@^1.0.0`: remove
`Signer` generic, move `permission.rules` to `permissionResponse.rules`,
rename `permissionResponse.address`→`from`,
`signerMeta.delegationManager`→`delegationManager`, and decoded
permission `signer...address`→`to`; applies across hooks, selectors,
components, and tests
> - Adds `wallet_getSupportedExecutionPermissions` (filters by enabled
advanced types) and `wallet_getGrantedExecutionPermissions`; wires
through `createMetamaskMiddleware` and forwards to the permissions
kernel snap
> - Bumps related deps (`eth-json-rpc-middleware@^23`,
`permissions-kernel-snap@^1.0.0`, `signature-controller@^39`,
`shield-controller@^5`, etc.) and adjusts LavaMoat policies to use the
updated middleware pathing
> - Updates PPOM/confirmation tests and stories to the new permission
shape; no functional changes beyond API alignment
> 
> <sup>Written by [Cursor
Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit
a522169. This will update automatically
on new commits. Configure
[here](https://cursor.com/dashboard?tab=bugbot).</sup>
<!-- /CURSOR_SUMMARY -->

---------

Co-authored-by: MetaMask Bot <metamaskbot@users.noreply.github.com>
wantedsystem pushed a commit to MetaMask/metamask-extension that referenced this pull request Jan 27, 2026
This PR updates the codebase to align with API changes in the
`@metamask/gator-permissions-controller` package.

**Reason for the change:**
The upstream `@metamask/gator-permissions-controller` package has
updated its type definitions and data structures. This PR ensures
compatibility with those changes.

**Changes included:**

1. **Type simplification**: Removed the `Signer` generic parameter from
`StoredGatorPermissionSanitized<Signer, PermissionTypesWithCustom>` →
`StoredGatorPermissionSanitized<PermissionTypesWithCustom>` across all
files (selectors, hooks, components, and tests).

2. **Data structure updates**:
- `permissionResponse.address` → `permissionResponse.from` (delegator
address)
- `decodedPermission.signer.data.address` → `decodedPermission.to`
(delegate/recipient address)
- `permissionResponse.signerMeta.delegationManager` →
`permissionResponse.delegationManager` (flattened structure)
- `permission.rules` → `permissionResponse.rules` (rules array location
change)

3. **New RPC methods**: Added support for two new unrestricted methods:
- `wallet_getSupportedExecutionPermissions` - Returns supported
permission types (filtered by enabled advanced permissions)
- `wallet_getGrantedExecutionPermissions` - Returns granted execution
permissions

[![Open in GitHub
Codespaces](https://github.com/codespaces/badge.svg)](https://codespaces.new/MetaMask/metamask-extension/pull/39176?quickstart=1)

<!--
If this PR is not End-User-Facing and should not show up in the
CHANGELOG, you can choose to either:
1. Write `CHANGELOG entry: null`
2. Label with `no-changelog`

If this PR is End-User-Facing, please write a short User-Facing
description in the past tense like:
`CHANGELOG entry: Added a new tab for users to see their NFTs`
`CHANGELOG entry: Fixed a bug that was causing some NFTs to flicker`

(This helps the Release Engineer do their job more quickly and
accurately)
-->

CHANGELOG entry: Added support for
`wallet_getSupportedExecutionPermissions` and
`wallet_getGrantedExecutionPermissions` RPC methods.
CHANGELOG entry: Updated to latest 7715 standart.

Depends on: MetaMask/core#7603
Relates to: MetaMask/snap-7715-permissions#249
Requires: MetaMask/core#7634
Requires: MetaMask/snap-7715-permissions#254

For manual testing check:
MetaMask/snap-7715-permissions#249

- [x] I've followed [MetaMask Contributor
Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask
Extension Coding
Standards](https://github.com/MetaMask/metamask-extension/blob/main/.github/guidelines/CODING_GUIDELINES.md).
- [x] I've completed the PR template to the best of my ability
- [x] I’ve included tests if applicable
- [x] I’ve documented my code using [JSDoc](https://jsdoc.app/) format
if applicable
- [x] I’ve applied the right labels on the PR (see [labeling
guidelines](https://github.com/MetaMask/metamask-extension/blob/main/.github/guidelines/LABELING_GUIDELINES.md)).
Not required for external contributors.

- [ ] I've manually tested the PR (e.g. pull and build branch, run the
app, test code being changed).
- [ ] I confirm that this PR addresses all acceptance criteria described
in the ticket it closes and includes the necessary testing evidence such
as recordings and or screenshots.

<!-- CURSOR_SUMMARY -->
---

> [!NOTE]
> Updates codebase to the 7715/gator-permissions v1 API and introduces
execution-permissions query RPCs.
>
> - Refactors to `@metamask/gator-permissions-controller@^1.0.0`: remove
`Signer` generic, move `permission.rules` to `permissionResponse.rules`,
rename `permissionResponse.address`→`from`,
`signerMeta.delegationManager`→`delegationManager`, and decoded
permission `signer...address`→`to`; applies across hooks, selectors,
components, and tests
> - Adds `wallet_getSupportedExecutionPermissions` (filters by enabled
advanced types) and `wallet_getGrantedExecutionPermissions`; wires
through `createMetamaskMiddleware` and forwards to the permissions
kernel snap
> - Bumps related deps (`eth-json-rpc-middleware@^23`,
`permissions-kernel-snap@^1.0.0`, `signature-controller@^39`,
`shield-controller@^5`, etc.) and adjusts LavaMoat policies to use the
updated middleware pathing
> - Updates PPOM/confirmation tests and stories to the new permission
shape; no functional changes beyond API alignment
>
> <sup>Written by [Cursor
Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit
a522169. This will update automatically
on new commits. Configure
[here](https://cursor.com/dashboard?tab=bugbot).</sup>
<!-- /CURSOR_SUMMARY -->

---------

Co-authored-by: MetaMask Bot <metamaskbot@users.noreply.github.com>
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.

6 participants