{ "prNumber": 44797, "prTitle": "release: 13.42.0", "generatedAt": "2026-07-30T21:06:31.082Z", "modelUsed": "gpt-5", "summary": { "totalFilesChanged": 1288, "totalCommitsInRelease": 144, "releaseRiskScore": "60/100", "highRiskScenarios": 7, "mediumRiskScenarios": 8 }, "testScenarios": { "cherryPickScenarios": [ { "area": "Security: Deep Link Interstitial Protection", "riskLevel": "high", "testSteps": [ "1. With the extension unlocked, open a MetaMask deep link that triggers an action (e.g., add token, add/switch network).", "2. Verify an interstitial confirmation appears showing the action and source; select Cancel and confirm no state changes.", "3. Repeat and Approve; verify the intended action executes and only once.", "4. Trigger the same deep link from an external site and confirm the same protection behavior." ], "whyThisMatters": "Cherry-pick 44830 fixes a regression where deep links could bypass the protective interstitial, which is a user safety boundary." }, { "area": "Deep Links: Missing Account Handling for Cross-Chain Asset Links", "riskLevel": "high", "testSteps": [ "1. Use a cross-chain asset deep link targeting a network not currently added or selected in the extension.", "2. Verify the UI gracefully prompts to add/switch network and/or select an account rather than crashing or landing on a broken screen.", "3. After adding/switching, confirm the link resolves to the correct asset view without state corruption." ], "whyThisMatters": "Cherry-pick 44913 fixes crashes or dead-ends when deep links reference assets on chains/accounts not yet available in the wallet." }, { "area": "Swaps: Stale Destination Exchange Rates", "riskLevel": "high", "testSteps": [ "1. Open Swaps, select a source token and rapidly change the destination token and/or network; observe the quoted rate.", "2. Wait for a short period and confirm the destination rate refreshes automatically and stays in sync with selections.", "3. Proceed to a quote and confirm that the final rate matches the most recent pre-submission rate (no stale carryover).", "4. Adjust slippage and verify the quote/rate recalculates correctly." ], "whyThisMatters": "Cherry-pick 45011 fixes stale destination quotes that can lead to incorrect expectations and potential value loss." }, { "area": "Accounts/Keyrings: Missing SLIP-44 Entries", "riskLevel": "high", "testSteps": [ "1. Connect a hardware wallet and add an account on a network with a non-standard coin type (e.g., Celo, RSK) after adding that network.", "2. Verify the derived address matches the expected path for that chain and does not mismatch previously imported addresses.", "3. Switch between networks and confirm the address stability and no derivation errors are shown." ], "whyThisMatters": "Cherry-pick 45039 fixes missing SLIP-44 mappings that can cause incorrect derivation paths, yielding wrong addresses especially on hardware wallets." }, { "area": "Hardware Wallets: Device Read Timeout during Account Creation", "riskLevel": "medium", "testSteps": [ "1. Start adding a Ledger/Trezor account, then simulate a stalled device read (do not confirm on device or disconnect).", "2. Verify the spinner stops after a reasonable timeout and a clear, actionable error is shown (e.g., Retry, Reconnect).", "3. Retry with the device properly connected/confirmed and ensure account import completes successfully." ], "whyThisMatters": "Cherry-pick 45053 fixes a stuck spinner that traps users when device reads hang, improving recovery and trust." }, { "area": "Balances: Loading Timer to Avoid Flicker/Stale Display", "riskLevel": "medium", "testSteps": [ "1. On a slow network or after locking/unlocking, observe the balance area; confirm a skeleton/placeholder appears before the balance renders.", "2. Rapidly switch networks and accounts and ensure no stale balances flash and the placeholder behavior is consistent.", "3. Check the popup and full-screen views to confirm consistent timing and no layout jank." ], "whyThisMatters": "Cherry-pick 45049 introduces a balance loading timer; incorrect timing can show stale values or cause confusing UI flicker." } ], "initialScenarios": [ { "area": "State Migration (Migration 219)", "riskLevel": "high", "testSteps": [ "1. Start on 13.41.x with: two software accounts, one hardware account, at least one custom network (RPC), several watched ERC-20 tokens and at least one NFT; have 1-2 connected sites and custom preferences set (currency, privacy).", "2. Upgrade to 13.42.0 and unlock; wait for any background sync to complete.", "3. Verify all accounts (including hardware) are present, selected account preserved, connected sites remain connected, and custom preferences persist.", "4. Confirm watched tokens and NFTs are still present with correct balances/fiat and no duplicated or missing assets across networks.", "5. Send a small transaction on a custom network to ensure post-migration signing/nonce/gas behavior is intact and activity history remains accessible." ], "whyThisMatters": "Data migrations can corrupt or drop user data (accounts, assets, networks). A faulty migration can silently break core wallet operations." }, { "area": "Token Management (Assets Controller v11 upgrade)", "riskLevel": "high", "testSteps": [ "1. On Ethereum mainnet, enable token detection and verify popular tokens auto-appear with correct name, symbol, decimals, and logos.", "2. Manually watch a custom ERC-20 by contract address and verify metadata (symbol/decimals) auto-resolves correctly; remove it and confirm fiat total updates immediately.", "3. Switch to a custom EVM network; add a token on that network and verify it does not bleed into mainnet and vice versa.", "4. Toggle token detection off/on and confirm asset lists are stable and no duplicates appear after refresh.", "5. Open a token’s details and ensure fiat conversion and recent activity reflect the correct network/token." ], "whyThisMatters": "A major Assets Controller change can impact token detection, metadata accuracy, and fiat conversions, directly affecting balances and user trust." }, { "area": "Transaction Signing and Activity Details", "riskLevel": "high", "testSteps": [ "1. From a dapp, submit a basic native transfer on Ethereum; review the confirmation screen (gas, total) and approve.", "2. After submission, open Activity and view transaction details; verify status progression (pending → confirmed) and correct fee/nonce data.", "3. Use Speed Up on a pending tx and confirm the original tx status reflects replacement.", "4. On an EIP-1559 L2 (e.g., Arbitrum/Optimism), repeat a send and confirm gas UI behaves correctly (max fee/priority) and accurate details render in Activity." ], "whyThisMatters": "Controller/UI changes can break core transaction flows and the accuracy of post-transaction details users rely on." }, { "area": "NFTs (Detection, Media Rendering, Placeholders)", "riskLevel": "medium", "testSteps": [ "1. Ensure the account holds at least one ERC-721 and one ERC-1155; open the NFTs tab and verify images/metadata load without broken placeholders.", "2. Open an NFT detail view and confirm attributes/description render and navigation is responsive.", "3. Switch between light and dark themes and confirm NFT images, badges, and placeholders remain visible and correctly styled.", "4. Import an NFT by contract + token ID and verify it appears with correct media or a graceful fallback if media fails." ], "whyThisMatters": "Large-scale UI and assets changes can break NFT rendering and degrade the asset gallery experience." }, { "area": "Message Encryption/Decryption (eth_getEncryptionPublicKey, eth_decrypt)", "riskLevel": "medium", "testSteps": [ "1. Connect a test dapp that requests eth_getEncryptionPublicKey; verify the permission/confirmation appears and approve.", "2. From the dapp, encrypt a message to the selected account, then initiate eth_decrypt; approve and verify the decrypted message matches the original.", "3. Switch accounts and retry decrypt; confirm the request targets the currently selected account and fails gracefully if keys don’t match.", "4. Reject a decrypt request and ensure the dapp receives a clear error and the extension shows no residual prompts." ], "whyThisMatters": "Subtle controller changes can disrupt encryption flows, impacting dapps that rely on secure messaging." }, { "area": "Alert System and Confirmation Modals", "riskLevel": "medium", "testSteps": [ "1. Initiate a site connection request from a new dapp; verify the connect modal shows correct site origin, permissions, and responsive layout.", "2. Trigger addEthereumChain and switchEthereumChain requests; confirm warning/interstitial copy is correct and Cancel leaves state unchanged.", "3. Initiate a signature request (personal_sign); verify warnings and details (origin, data) are clear and that Reject returns control to the dapp cleanly." ], "whyThisMatters": "Wide UI refactors risk breaking critical interstitials and confirmations that protect users when granting permissions." }, { "area": "Analytics Consent (MetaMetrics Controller/Adapter)", "riskLevel": "medium", "testSteps": [ "1. Fresh install → decline MetaMetrics; perform common actions (connect site, send tx) and confirm no analytics network calls occur (check DevTools → Network for analytics endpoints).", "2. Enable MetaMetrics in Settings → Advanced; perform actions again and verify events now appear, then disable and confirm events stop.", "3. Ensure enabling/disabling does not require reload and doesn’t break normal wallet operations." ], "whyThisMatters": "Analytics changes can create privacy regressions or cause runtime errors if events fire at the wrong time." }, { "area": "Network Management (Add/Remove/Switch Custom RPC)", "riskLevel": "medium", "testSteps": [ "1. Add a custom network with chain ID (numeric or hex), symbol, and block explorer; save and switch to it.", "2. Confirm balances load and activity filters correctly to the selected network.", "3. Switch between Mainnet and the custom network multiple times and verify address consistency and no stale balances.", "4. Remove the custom network and ensure the UI returns to a default network without errors." ], "whyThisMatters": "Controller and UI changes can break chain metadata handling, causing failed balance loads or address mismatches." }, { "area": "Dapp Error Handling (API Error Handler)", "riskLevel": "medium", "testSteps": [ "1. From a dapp, send a transaction designed to revert (e.g., failing require) and approve in the extension.", "2. After failure, verify the UI shows a clear, user-friendly error with revert reason (if available), not raw or cryptic RPC errors.", "3. Confirm the Activity entry reflects failure accurately and offers appropriate actions (e.g., view on explorer)." ], "whyThisMatters": "Recent error handling changes risk exposing raw errors or misinforming users about transaction outcomes." } ] } }