chore(runway): cherry-pick fix: cp-7.60.0 non-evm accounts not found

[runway-github]

• fix: cp-7.60.0 non-evm accounts not found (fix: cp-7.60.0 non-evm accounts not found #23318)

Description

Fix Non-EVM accounts not found
Fixes part of this
MetaMask/metamask-extension#38104

Changelog

CHANGELOG entry: fix: non-evm accounts not found

Related issues

Fixes: MetaMask/metamask-extension#38104

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

• I’ve followed MetaMask Contributor
  Docs and MetaMask Mobile
  Coding
  Standards.
• 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 format
  if applicable
• I’ve applied the right labels on the PR (see labeling
  guidelines).
  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.

---

Note

Upgrade snaps dependencies in package.json: @metamask/solana-wallet-snap to ^2.5.0 and @metamask/tron-wallet-snap to ^1.13.0 (with lockfile updates).

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

ec74886

[github-actions]

CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes.

[github-actions]

🔍 Smart E2E Test Selection

• Selected E2E tags: SmokeCore, SmokeAccounts, SmokeAssets, SmokeSwaps, SmokeConfirmationsRedesigned, SmokeWalletPlatform
• Risk Level: high
• AI Confidence: 45%

click to see 🤖 AI reasoning details

The changes are to package.json and yarn.lock, which are critical dependency management files. Without access to the git diff, I cannot determine the exact nature or scope of the dependency changes.

Key considerations:

1. Critical Files: package.json is pre-marked as critical, and dependency changes can have cascading effects throughout the application
2. Unknown Scope: Unable to see which specific dependencies changed, their version bumps, or if new dependencies were added
3. Potential Impact Areas: Dependency changes could affect:
   • Core wallet functionality (controllers, Engine)
   • Asset management and display
   • Network abstractions and connections
   • UI components and user flows
   • Transaction handling and confirmations
   • Account management

Risk Assessment:

• High Risk: Because these are dependency files in a financial application where bugs could lead to loss of funds or security issues
• Conservative Approach: Running core smoke tests to ensure critical paths remain functional after dependency updates

Selected Tags Rationale:

• SmokeCore: Core wallet functionality must be verified
• SmokeAccounts: Account management could be affected by controller or crypto library updates
• SmokeAssets: Asset display and management relies on various dependencies
• SmokeSwaps: Swap functionality involves multiple dependencies
• SmokeConfirmationsRedesigned: Transaction confirmations are critical and could be affected
• SmokeWalletPlatform: Core wallet and platform operations

Confidence Level: 45/100 (Low-Medium)

• Cannot see actual changes in the diff
• Unknown which dependencies were modified
• Conservative approach warranted given the criticality of the application
• Would prefer to see the specific dependency changes to make a more informed decision

View GitHub Actions results

[socket-security]

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

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	npm/​@​metamask/​tron-wallet-snap@​1.12.1 ⏵ 1.13.0				+1
	npm/​@​metamask/​solana-wallet-snap@​2.4.7 ⏵ 2.5.0	-3			+1

View full report

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[metamaskbot]

No release label on PR. Adding release label release-7.60.0 on PR, as PR was cherry-picked in branch 7.60.0.