Skip to content

chore(runway): cherry-pick chore: bump @metamask/tron-wallet-snap to 1.25.6#30768

Merged
gabrieledm merged 1 commit into
release/7.79.0from
cherry-pick-7-79-0-2bb066b
May 28, 2026
Merged

chore(runway): cherry-pick chore: bump @metamask/tron-wallet-snap to 1.25.6#30768
gabrieledm merged 1 commit into
release/7.79.0from
cherry-pick-7-79-0-2bb066b

Conversation

@runway-github

@runway-github runway-github Bot commented May 28, 2026

Copy link
Copy Markdown
Contributor

Description

This PR bumps @metamask/tron-wallet-snap from ^1.25.3 to ^1.25.6.

The main purpose of this update is to pull in the latest Tron snap
validation fixes, in particular a mechanism to refresh stale or invalid
expiration, ref_block_bytes and ref_block_hash before signing in
both send/broadcast paths.

Preview package:

  • @metamask-previews/tron-wallet-snap@1.25.3-preview-995ddc5

Release:

  • @metamask-previews/tron-wallet-snap@^1.25.6

Upstream PR:

Changelog

CHANGELOG entry: bump the @metamask/tron-wallet-snap to ^1.25.6

Related issues

n/a

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

Performance checks (if applicable)

  • I've tested on Android
    • Ideally on a mid-range device; emulator is acceptable
  • I've tested with a power user scenario
  • Use these power-user
    SRPs

    to import wallets with many accounts and tokens
  • I've instrumented key operations with Sentry traces for production
    performance metrics
  • See trace() for usage and
    addToken
    for an example

For performance guidelines and tooling, see the Performance
Guide
.

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
Touches Tron signing and broadcast behavior via the wallet snap; scope
is limited to a patch dependency bump with no local code edits, but
failed or incorrect ref-block handling could still affect Tron sends.

Overview
Bumps @metamask/tron-wallet-snap from ^1.25.3 to ^1.25.6 in
package.json and yarn.lock, with an Unreleased changelog entry.
There are no application source changes in this repo—the mobile app
picks up upstream snap behavior from the new package version.

Per the PR intent, 1.25.6 brings Tron transaction validation
fixes, notably refreshing stale or invalid expiration,
ref_block_bytes, and ref_block_hash before signing
on send and
broadcast paths.

Reviewed by Cursor Bugbot for commit
b958d77. Bugbot is set up for automated
code reviews on this repo. Configure
here.


Co-authored-by: gabrieledm gabriele.delmonte@proton.me
Co-authored-by: Gabriele Del Monte 37625739+gabrieledm@users.noreply.github.com 2bb066b

This PR bumps @metamask/tron-wallet-snap from `^1.25.3` to `^1.25.6`.

The main purpose of this update is to pull in the latest Tron snap
validation fixes, in particular a mechanism to refresh stale or invalid
`expiration`, `ref_block_bytes` and `ref_block_hash` before signing in
both send/broadcast paths.

Preview package:
- `@metamask-previews/tron-wallet-snap@1.25.3-preview-995ddc5`

Release:
- `@metamask-previews/tron-wallet-snap@^1.25.6`

Upstream PR:
- MetaMask/snap-tron-wallet#305

CHANGELOG entry: bump the `@metamask/tron-wallet-snap` to `^1.25.6`

n/a

```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] -->

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

<!--
Every checklist item must be consciously assessed before marking this PR
as
"Ready for review". A checked box means you deliberately considered that
responsibility, not that you literally performed every action listed.

Unchecked boxes are ambiguous: they are not an implicit "N/A" and they
are not
a silent "skip". See `docs/readme/ready-for-review.md` for the full
checklist
semantics.
-->

- [ ] 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).
- [X] I've completed the PR template to the best of my ability
- [X] I've included tests if applicable
- [ ] 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-mobile/blob/main/.github/guidelines/LABELING_GUIDELINES.md)).
Not required for external contributors.

- [ ] I've tested on Android
  - Ideally on a mid-range device; emulator is acceptable
- [ ] I've tested with a power user scenario
- Use these [power-user
SRPs](https://consensyssoftware.atlassian.net/wiki/spaces/TL1/pages/edit-v2/401401446401?draftShareId=9d77e1e1-4bdc-4be1-9ebb-ccd916988d93)
to import wallets with many accounts and tokens
- [ ] I've instrumented key operations with Sentry traces for production
performance metrics
- See [`trace()`](/app/util/trace.ts) for usage and
[`addToken`](/app/components/Views/AddAsset/components/AddCustomToken/AddCustomToken.tsx#L274)
for an example

For performance guidelines and tooling, see the [Performance
Guide](https://consensyssoftware.atlassian.net/wiki/spaces/TL1/pages/400085549067/Performance+Guide+for+Engineers).

<!--
Reviewer checklist items follow the same semantics as the author
checklist: an
unchecked box is ambiguous, a checked box means the reviewer consciously
assessed that responsibility. See `docs/readme/ready-for-review.md`.
-->

- [ ] 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**
> Touches Tron signing and broadcast behavior via the wallet snap; scope
is limited to a patch dependency bump with no local code edits, but
failed or incorrect ref-block handling could still affect Tron sends.
>
> **Overview**
> Bumps **`@metamask/tron-wallet-snap`** from `^1.25.3` to `^1.25.6` in
`package.json` and `yarn.lock`, with an **Unreleased** changelog entry.
There are **no application source changes** in this repo—the mobile app
picks up upstream snap behavior from the new package version.
>
> Per the PR intent, **1.25.6** brings Tron transaction validation
fixes, notably **refreshing stale or invalid `expiration`,
`ref_block_bytes`, and `ref_block_hash` before signing** on send and
broadcast paths.
>
> <sup>Reviewed by [Cursor Bugbot](https://cursor.com/bugbot) for commit
b958d77. Bugbot is set up for automated
code reviews on this repo. Configure
[here](https://www.cursor.com/dashboard/bugbot).</sup>
<!-- /CURSOR_SUMMARY -->

---------

Co-authored-by: gabrieledm <gabriele.delmonte@proton.me>
Co-authored-by: Gabriele Del Monte <37625739+gabrieledm@users.noreply.github.com>
@metamaskbotv2 metamaskbotv2 Bot added the team-bots Bot team (for MetaMask Bot, Runway Bot, etc.) label May 28, 2026
@github-actions

Copy link
Copy Markdown
Contributor

🔍 Smart E2E Test Selection

⏭️ Smart E2E selection skipped - PR targets a release or stable branch (release/* or stable)

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/​tron-wallet-snap@​1.25.3 ⏵ 1.25.810010097 +198 +1100

View full report

@github-actions

Copy link
Copy Markdown
Contributor

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.

@vpintorico vpintorico enabled auto-merge (squash) May 28, 2026 19:33
@gabrieledm gabrieledm disabled auto-merge May 28, 2026 20:04
@gabrieledm gabrieledm enabled auto-merge (squash) May 28, 2026 20:04
@gabrieledm gabrieledm merged commit 9bb2e22 into release/7.79.0 May 28, 2026
297 of 305 checks passed
@gabrieledm gabrieledm deleted the cherry-pick-7-79-0-2bb066b branch May 28, 2026 20:41
@github-actions github-actions Bot locked and limited conversation to collaborators May 28, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

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