Skip to content

chore(runway): cherry-pick chore: bump @metamask/tron-wallet-snap to version 1.19.0 cp-7.61.6#24378

Merged
joaoloureirop merged 1 commit into
release/7.61.6from
runway-cherry-pick-7.61.6-1767985518
Jan 9, 2026
Merged

chore(runway): cherry-pick chore: bump @metamask/tron-wallet-snap to version 1.19.0 cp-7.61.6#24378
joaoloureirop merged 1 commit into
release/7.61.6from
runway-cherry-pick-7.61.6-1767985518

Conversation

@runway-github
Copy link
Copy Markdown
Contributor

@runway-github runway-github Bot commented Jan 9, 2026

Description

Changelog

CHANGELOG entry: null

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

Upgrades dependency to latest patch version.

  • Bumps @metamask/tron-wallet-snap from ^1.17.0 to ^1.19.0 in package.json
  • Updates yarn.lock to resolve the new version

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

Co-authored-by: Alejandro Garcia Anglada aganglada@gmail.com 72cd316

…version 1.19.0 cp-7.61.6 (#24365)

<!--
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**

<!--
Write a short description of the changes included in this pull request,
also include relevant motivation and context. Have in mind the following
questions:
1. What is the reason for the change?
2. What is the improvement/solution?
-->

## **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: null

## **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]
> Updates dependency to latest minor version.
> 
> - Upgrades `@metamask/tron-wallet-snap` from `^1.17.0` to `^1.19.0` in
`package.json`; refreshes `yarn.lock` accordingly
> 
> <sup>Written by [Cursor
Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit
460a33e. This will update automatically
on new commits. Configure
[here](https://cursor.com/dashboard?tab=bugbot).</sup>
<!-- /CURSOR_SUMMARY -->

Co-authored-by: Alejandro Garcia Anglada <aganglada@gmail.com>
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Jan 9, 2026

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.

@metamaskbot metamaskbot added the team-bots Bot team (for MetaMask Bot, Runway Bot, etc.) label Jan 9, 2026
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Jan 9, 2026

🔍 Smart E2E Test Selection

  • Selected E2E tags: SmokeCore, SmokeWalletPlatform, SmokeConfirmationsRedesigned, SmokeNetworkAbstractions, SmokeAccounts, SmokeTrade, SmokeMultiChainAPI, SmokeMultiChainPermissions, SmokeSwaps
  • Risk Level: high
  • AI Confidence: 85%
click to see 🤖 AI reasoning details

This PR involves updating multiple critical MetaMask controller packages that form the foundation of wallet operations:

High-Risk Changes:

  1. Transaction Controller (^62.3.0 → ^62.6.0): Core component for all transaction handling, confirmations, and transaction lifecycle management. Used extensively across the app in 30+ files.

  2. Network Controller (^25.0.0 → ^27.1.0): A major version jump (2 major versions) for a critical controller managing all network operations. Used in 30+ files throughout the app.

  3. Bridge Controller: Now includes a new patch, affecting bridge and multi-chain transaction flows. Used in 30+ files with functions like formatChainIdToCaip, isSolanaChainId, isBitcoinChainId.

  4. Snaps Controllers: Now patched, affecting snaps ecosystem which is fundamental to keyring management and account operations.

  5. Profile Metrics Controller: Newly added controller, indicating new functionality for metrics tracking.

  6. Chain-Agnostic Permission: Updated, affecting multi-chain permission management.

  7. Multichain API packages: Both client and middleware updated, affecting multi-chain operations.

Selected Test Tags Rationale:

  • SmokeCore: Essential due to major controller updates affecting core wallet functionality
  • SmokeWalletPlatform: Critical for testing core wallet operations with updated controllers
  • SmokeConfirmationsRedesigned: Transaction controller changes directly impact all confirmation flows
  • SmokeNetworkAbstractions: Network controller major version jump requires comprehensive network layer testing
  • SmokeAccounts: Account management could be affected by keyring and controller changes
  • SmokeTrade: Bridge controller changes affect trading and swap operations
  • SmokeMultiChainAPI: Direct updates to multichain-api-client and middleware
  • SmokeMultiChainPermissions: Chain-agnostic-permission updates require testing
  • SmokeSwaps: Swap controller and bridge changes affect swap functionality

Not selected but considered:

  • SmokeStake, SmokeCard, SmokeNotifications, SmokePerps: While stake-sdk was updated, these are more isolated features
  • SmokeRamps: No direct changes to ramp-related controllers
  • SmokeNetworkExpansion: Covered by SmokeNetworkAbstractions

The risk level is HIGH because multiple core controllers were updated including two major version jumps for Network Controller, and these changes affect critical wallet operations including transactions, network management, multi-chain support, and permissions.

View GitHub Actions results

@joaoloureirop joaoloureirop enabled auto-merge (squash) January 9, 2026 19:12
@joaoloureirop joaoloureirop disabled auto-merge January 9, 2026 19:19
@joaoloureirop joaoloureirop enabled auto-merge (squash) January 9, 2026 19:24
@joaoloureirop joaoloureirop disabled auto-merge January 9, 2026 19:24
@joaoloureirop joaoloureirop merged commit 223de32 into release/7.61.6 Jan 9, 2026
47 checks passed
@joaoloureirop joaoloureirop deleted the runway-cherry-pick-7.61.6-1767985518 branch January 9, 2026 19:25
@github-actions github-actions Bot locked and limited conversation to collaborators Jan 9, 2026
@metamaskbot metamaskbot added the release-7.61.6 Issue or pull request that will be included in release 7.61.6 label Jan 12, 2026
@metamaskbot
Copy link
Copy Markdown
Collaborator

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

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

release-7.61.6 Issue or pull request that will be included in release 7.61.6 size-XS 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