chore: update @metamask/keyring-api and @metamask/tron-wallet-snap versions

[baptiste-marchand]

Following MetaMask/metamask-extension#38466 :

• Bump @metamask/tron-wallet-snap to v1.15.1
• Bump @metamask/keyring-api to v21.3.0

This PR is required before enabling Tron dApp connectivity support.

Description

Changelog

CHANGELOG entry:

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

• 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

Updates TRX transaction signing check to TrxMethod.SignMessage and bumps @metamask/keyring-api and @metamask/tron-wallet-snap versions.

• Selectors:
  • Update selectCanSignTransactions to check TrxMethod.SignMessage (replacing SignMessageV2).
• Tests:
  • Adjust accountsController.test.ts to use TRX Account with SignMessage and TrxMethod.SignMessage.
• Dependencies:
  • Bump @metamask/keyring-api to ^21.3.0.
  • Bump @metamask/tron-wallet-snap to ^1.15.1.
  • Update yarn.lock accordingly.

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

[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.

[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.13.0 ⏵ 1.15.1	+1		+1	+1
	npm/​@​metamask/​keyring-api@​21.2.0 ⏵ 21.3.0	+1			+1

View full report

[github-actions]

🔍 Smart E2E Test Selection

• Selected E2E tags: SmokeAccounts, SmokeTrade, SmokeNetworkExpansion, SmokeStake
• Risk Level: medium
• AI Confidence: 75%

click to see 🤖 AI reasoning details

The changes involve:

1. Tron Method Rename: The selector selectCanSignTransactions has been updated from TrxMethod.SignMessageV2 to TrxMethod.SignMessage. This aligns with a change in the Tron wallet snap API.

2. Package Updates:

   • @metamask/keyring-api upgraded from 21.2.0 to 21.3.0
   • @metamask/tron-wallet-snap upgraded from 1.13.0 to 1.15.1

The selectCanSignTransactions selector is used in:

• Bridge functionality (app/core/redux/slices/bridge/index.ts) - affects whether swaps/bridge are enabled
• Multi-chain account management components

Impact areas:

• SmokeAccounts: The selector is core to account management and determines if accounts can sign transactions. This is critical for account functionality.
• SmokeTrade: The selector affects selectIsSwapsEnabled in the bridge slice, directly impacting swap/trade functionality.
• SmokeNetworkExpansion: Tron is a non-EVM chain, so changes to Tron support fall under network expansion testing.
• SmokeStake: The Tron wallet snap is used for Tron staking functionality (as seen in the useTronStake hooks).

The risk is medium because:

• The change is narrow (single method rename) but touches critical transaction signing capability detection
• Package updates could introduce behavioral changes
• The code path is used by bridge/swap functionality which is financially sensitive
• However, the change appears to be a straightforward API alignment with the updated packages

View GitHub Actions results

[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