chore: bump @metamask/transaction-controller and @metamask/transaction-pay-controller

[dan437]

Description

Bump @metamask/transaction-controller from ^64.0.0 to ^64.2.0 and @metamask/transaction-pay-controller from ^19.1.0 to ^19.1.1.

Core PR: MetaMask/core#8447

Changelog

CHANGELOG entry: null

Related issues

Fixes: CONF-1158

Manual testing steps

Feature: mm_pay_time_to_complete_s accuracy

  Scenario: Perps withdraw reports realistic time
    Given the user has a Hyperliquid perps position

    When user initiates a perps withdraw
    Then Transaction Finalized event contains mm_pay_time_to_complete_s > 1s

  Scenario: Perps deposit reports realistic time
    Given the user has funds available for a perps deposit

    When user initiates a perps deposit
    Then Transaction Finalized event contains mm_pay_time_to_complete_s > 1s

  Scenario: Predict withdraw reports realistic time
    Given the user has a predict position to withdraw

    When user initiates a predict withdraw
    Then Transaction Finalized event contains mm_pay_time_to_complete_s > 1s

Screenshots/Recordings

N/A — metric-only change, no UI impact.

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

Medium Risk
Updates core transaction/payment controller dependencies, which can affect transaction lifecycle behavior and related metrics. Risk is moderate because changes are pulled in via upstream packages rather than local code edits.

Overview
Updates dependencies to @metamask/transaction-controller@^64.2.0 (from ^64.0.0) and @metamask/transaction-pay-controller@^19.1.1 (from ^19.1.0).

Regenerates yarn.lock to reflect the new transitive graph, including a bump of @metamask/ramps-controller to 13.1.0 and updated internal controller dependencies (e.g., @metamask/accounts-controller, @metamask/messenger).

^{Reviewed by Cursor Bugbot for commit 30db948. Bugbot is set up for automated code reviews on this repo. 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/​ramps-controller@​13.0.0 ⏵ 13.1.0				+1
	npm/​@​metamask/​transaction-pay-controller@​19.1.0 ⏵ 19.1.1	+1		+1	+1

View full report

[github-actions]

🔍 Smart E2E Test Selection

• Selected E2E tags: SmokeAccounts, SmokeConfirmations, SmokeIdentity, SmokeNetworkAbstractions, SmokeNetworkExpansion, SmokeTrade, SmokeWalletPlatform, SmokeCard, SmokePerps, SmokeRamps, SmokeMultiChainAPI, SmokePredictions, SmokeSeedlessOnboarding, FlaskBuildTests
• Selected Performance tags: @PerformanceAccountList, @PerformanceOnboarding, @PerformanceLogin, @PerformanceSwaps, @PerformanceLaunch, @PerformanceAssetLoading, @PerformancePredict, @PerformancePreps
• Risk Level: high
• AI Confidence: 100%

click to see 🤖 AI reasoning details

E2E Test Selection:
Hard rule (controller-version-update): @MetaMask controller package version updated in package.json: @metamask/transaction-controller, @metamask/transaction-pay-controller. Running all tests.

Performance Test Selection:
Hard rule (controller-version-update): @MetaMask controller package version updated in package.json: @metamask/transaction-controller, @metamask/transaction-pay-controller. Running all tests.

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

[github-actions]

✅ E2E Fixture Validation — Schema is up to date
11 value mismatches detected (expected — fixture represents an existing user).
View details