Skip to content

chore(runway): cherry-pick 2513c6f#27374

Merged
chloeYue merged 1 commit into
release/7.68.1from
runway-metamask-blockchain-wall-ios3-7.68.1-cherry-picked-commits
Mar 11, 2026
Merged

chore(runway): cherry-pick 2513c6f#27374
chloeYue merged 1 commit into
release/7.68.1from
runway-metamask-blockchain-wall-ios3-7.68.1-cherry-picked-commits

Conversation

@runway-github

@runway-github runway-github Bot commented Mar 11, 2026

Copy link
Copy Markdown
Contributor

Description

This bumps Snaps dependencies to the latest versions.

Changelog

CHANGELOG entry: Add support for additional icon colors in Snaps Icon
component.

Related issues

Fixes:

Manual testing steps

Feature: my feature name

  Scenario: user [verb for user action]
    Given [describe expected initial app state]

    When user [verb for user action]
    Then [describe expected outcome]

Screenshots/Recordings

Before

After

Pre-merge author checklist

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.

Note

Medium Risk
Updates multiple @metamask/snaps-* packages and wires new/changed
SnapInterface controller actions, which could subtly affect Snap UI
rendering and interface lifecycle behavior. Main functional change is
limited, but dependency upgrades and messenger action-surface changes
increase regression risk.

Overview
Bumps Snaps dependencies (notably @metamask/snaps-sdk to
^11.0.0 and related snaps-controllers, snaps-rpc-methods,
snaps-utils, execution environments), updating yarn.lock
accordingly.

Extends the Snap UI Icon renderer to support additional color
variants (error, warning, success). Aligns Snap interface plumbing
with updated controller APIs by switching getInterfaceState to call
SnapInterfaceController:getInterfaceState, adding
SnapInterfaceController:setInterfaceDisplayed to allowed messenger
actions/permission specs, and updating Snap UI test utilities to include
displayed: true. Also bumps the test-snaps fixture URL to 3.4.1.

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

[2513c6f](https://github.com/MetaMask/metamask-mobile/commit/2513c6fd253f16f2c75dfeb4fe015509b69c516b)

<!--
Please submit this PR as a draft initially.
Do not mark it as "Ready for review" until the template has been
completely filled out, and PR status checks have passed at least once.
-->

## **Description**

This bumps Snaps dependencies to the latest versions.

## **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: Add support for additional icon colors in Snaps `Icon`
component.

## **Related issues**

Fixes:

## **Manual testing steps**

```gherkin
Feature: my feature name

  Scenario: user [verb for user action]
    Given [describe expected initial app state]

    When user [verb for user action]
    Then [describe expected outcome]
```

## **Screenshots/Recordings**

<!-- If applicable, add screenshots and/or recordings to visualize the
before and after of your change. -->

### **Before**

<!-- [screenshots/recordings] -->

### **After**

<!-- [screenshots/recordings] -->

## **Pre-merge author checklist**

- [ ] I've followed [MetaMask Contributor
Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask Mobile
Coding
Standards](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/CODING_GUIDELINES.md).
- [ ] I've completed the PR template to the best of my ability
- [ ] I've included tests if applicable
- [ ] I've documented my code using [JSDoc](https://jsdoc.app/) format
if applicable
- [ ] I've applied the right labels on the PR (see [labeling
guidelines](https://github.com/MetaMask/metamask-mobile/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]
> **Medium Risk**
> Updates multiple `@MetaMask/snaps-*` packages and wires new/changed
SnapInterface controller actions, which could subtly affect Snap UI
rendering and interface lifecycle behavior. Main functional change is
limited, but dependency upgrades and messenger action-surface changes
increase regression risk.
> 
> **Overview**
> **Bumps Snaps dependencies** (notably `@metamask/snaps-sdk` to
`^11.0.0` and related `snaps-controllers`, `snaps-rpc-methods`,
`snaps-utils`, execution environments), updating `yarn.lock`
accordingly.
> 
> Extends the Snap UI `Icon` renderer to support additional color
variants (`error`, `warning`, `success`). Aligns Snap interface plumbing
with updated controller APIs by switching `getInterfaceState` to call
`SnapInterfaceController:getInterfaceState`, adding
`SnapInterfaceController:setInterfaceDisplayed` to allowed messenger
actions/permission specs, and updating Snap UI test utilities to include
`displayed: true`. Also bumps the test-snaps fixture URL to `3.4.1`.
> 
> <sup>Written by [Cursor
Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit
0702f6e. This will update automatically
on new commits. Configure
[here](https://cursor.com/dashboard?tab=bugbot).</sup>
<!-- /CURSOR_SUMMARY -->
@runway-github runway-github Bot requested review from a team as code owners March 11, 2026 17:07
@metamaskbot metamaskbot added the team-bots Bot team (for MetaMask Bot, Runway Bot, etc.) label Mar 11, 2026
@github-actions

Copy link
Copy Markdown
Contributor

🔍 Smart E2E Test Selection

⏭️ Smart E2E selection skipped - base branch is not main (base: release/7.68.1)

All E2E tests pre-selected.

View GitHub Actions results

@socket-security

Copy link
Copy Markdown

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff Package Supply Chain
Security
Vulnerability Quality Maintenance License
Updatednpm/​@​metamask/​snaps-controllers@​18.0.2 ⏵ 18.0.471 +110076 +198 +250
Addednpm/​@​metamask/​snaps-rpc-methods@​15.0.098100769650
Updatednpm/​@​metamask/​snaps-execution-environments@​11.0.0 ⏵ 11.0.199 +11007797 +180

View full report

@socket-security

Copy link
Copy Markdown

Caution

MetaMask internal reviewing guidelines:

  • Do not ignore-all
  • Each alert has instructions on how to review if you don't know what it means. If lost, ask your Security Liaison or the supply-chain group
  • Copy-paste ignore lines for specific packages or a group of one kind with a note on what research you did to deem it safe.
    @SocketSecurity ignore npm/PACKAGE@VERSION
Action Severity Alert  (click "▶" to expand/collapse)
Block High
Publisher changed: npm ses is now published by boneskull

Author: boneskull

From: ?npm/@metamask/profile-sync-controller@27.1.0npm/@metamask/account-tree-controller@4.1.1npm/@metamask/multichain-transactions-controller@7.0.1npm/@metamask/multichain-account-service@7.0.0npm/@metamask/assets-controller@2.0.0npm/@metamask/bridge-controller@66.2.0npm/@metamask/bridge-status-controller@66.1.0npm/@metamask/accounts-controller@36.0.1npm/@metamask/assets-controllers@100.0.3npm/@metamask/transaction-pay-controller@16.1.2npm/@metamask/snaps-utils@12.1.1npm/@metamask/gator-permissions-controller@0.3.0npm/ses@1.15.0

ℹ Read more on: This package | This alert | What is unstable ownership?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Try to reduce the number of authors you depend on to reduce the risk to malicious actors gaining access to your supply chain. Packages should remove inactive collaborators with publishing rights from packages on npm.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/ses@1.15.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Block Low
Publisher changed: npm ses is now published by boneskull instead of kriskowal

New Author: boneskull

Previous Author: kriskowal

From: ?npm/@metamask/profile-sync-controller@27.1.0npm/@metamask/account-tree-controller@4.1.1npm/@metamask/multichain-transactions-controller@7.0.1npm/@metamask/multichain-account-service@7.0.0npm/@metamask/assets-controller@2.0.0npm/@metamask/bridge-controller@66.2.0npm/@metamask/bridge-status-controller@66.1.0npm/@metamask/accounts-controller@36.0.1npm/@metamask/assets-controllers@100.0.3npm/@metamask/transaction-pay-controller@16.1.2npm/@metamask/snaps-utils@12.1.1npm/@metamask/gator-permissions-controller@0.3.0npm/ses@1.15.0

ℹ Read more on: This package | This alert | What is new author?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Scrutinize new collaborator additions to packages because they now have the ability to publish code into your dependency tree. Packages should avoid frequent or unnecessary additions or changes to publishing rights.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/ses@1.15.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

@chloeYue chloeYue left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

LGTM

@chloeYue chloeYue merged commit 8365b6c into release/7.68.1 Mar 11, 2026
104 of 105 checks passed
@chloeYue chloeYue deleted the runway-metamask-blockchain-wall-ios3-7.68.1-cherry-picked-commits branch March 11, 2026 18:18
@github-actions github-actions Bot locked and limited conversation to collaborators Mar 11, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

size-S team-bots Bot team (for MetaMask Bot, Runway Bot, etc.)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants