{ "prNumber": 47119, "prTitle": "release: 13.54.0", "generatedAt": "2026-10-23T03:15:51.297Z", "modelUsed": "gpt-5", "summary": { "totalFilesChanged": 587, "totalCommitsInRelease": 111, "releaseRiskScore": "56/100", "highRiskScenarios": 6, "mediumRiskScenarios": 7 }, "testScenarios": { "cherryPickScenarios": [ { "area": "Snaps: Tron Snap update (connect, sign transaction, permissions)", "riskLevel": "medium", "testSteps": [ "1. Install/connect the Tron Snap from a known demo dapp and approve requested permissions.", "2. View Tron account details in the Snap UI and send a small TRX transfer from the demo dapp.", "3. Verify the confirmation screen data (to, amount, fee) and that the transaction status updates to confirmed.", "4. Revoke the Snap’s permissions and ensure subsequent dapp requests are blocked or prompt re-approval." ], "whyThisMatters": "Cherry-pick 47122 bumps Tron Snap; Snap permission/signing flows can break on version changes, risking failed sends or incorrect confirmations." }, { "area": "Snaps: Solana Snap update (connect, sign, message signing)", "riskLevel": "medium", "testSteps": [ "1. Connect a Solana Snap via a demo dapp and approve all requested capabilities.", "2. Initiate a SOL transfer and confirm the MetaMask Snap confirmation displays correct details.", "3. Request a message/signData operation and ensure it signs and returns as expected.", "4. Switch accounts and retry; confirm the Snap respects the selected account and permissions." ], "whyThisMatters": "Cherry-pick 47122 updates Solana Snap; changes may affect signing formats and account routing, causing user-facing errors." }, { "area": "Snaps: Stellar Wallet Snap update (connect, sign transaction)", "riskLevel": "medium", "testSteps": [ "1. Connect the Stellar Wallet Snap from a demo dapp and grant permissions.", "2. Send a small XLM transfer via the dapp and confirm the transaction through the Snap UI.", "3. Verify post-send details (hash, status) appear correctly in the dapp and MetaMask activity if surfaced.", "4. Disconnect the Snap and confirm the dapp cannot initiate further requests without re-connection." ], "whyThisMatters": "Cherry-pick 47224 updates the Stellar Snap; permission and signing behavior can change with Snap versions and must be validated." } ], "initialScenarios": [ { "area": "State Migrations (231–233): NFT detection and asset preferences", "riskLevel": "high", "testSteps": [ "1. Start with a 13.53.x profile having NFT detection OFF and 2 manually imported NFTs on Ethereum.", "2. Upgrade to 13.54.0 and open the NFTs tab for the same account and network.", "3. Verify previously imported NFTs still appear once, with correct metadata and no duplicates.", "4. Toggle NFT detection ON, refresh the NFTs tab, and confirm no duplicate entries are created for already imported NFTs." ], "whyThisMatters": "Migrations can inadvertently drop or duplicate user assets; manual NFT imports and detection settings are persistent user data that must not regress." }, { "area": "State Migrations (231–233): Network enablement and asset fetch behavior", "riskLevel": "high", "testSteps": [ "1. Use a pre-upgrade profile with multiple networks configured (e.g., Ethereum Mainnet, Polygon, BSC) and token auto-detection OFF for Polygon.", "2. Upgrade to 13.54.0 and open the Assets tab on Polygon.", "3. Verify token lists are not auto-fetched for networks that previously had detection disabled and existing tokens remain intact.", "4. Enable token detection for Polygon, reopen the Assets tab, and confirm the list updates without overwriting/removing user-added tokens." ], "whyThisMatters": "Network enablement logic impacts background asset fetching; incorrect defaults or migrations can cause unexpected RPC traffic or missing tokens." }, { "area": "Transaction Sending: EIP-1559 fee estimation and speed-up/cancel (Transaction Pay Controller patch)", "riskLevel": "high", "testSteps": [ "1. On Ethereum Mainnet, send a standard ETH transfer using the default suggested gas (EIP-1559) and submit.", "2. From the activity view, speed up the pending transaction using a higher priority and confirm it is replaced and mined.", "3. Send another transaction and cancel it before it is mined; verify final statuses reflect 'Cancelled' cleanly in activity and state.", "4. Confirm the network fee is calculated and displayed consistently across the confirm screen and activity details." ], "whyThisMatters": "A patched transaction-pay dependency can break fee estimation or replacement logic, causing user loss or stuck transactions." }, { "area": "Transaction Sending: Legacy gas on non-1559 networks", "riskLevel": "high", "testSteps": [ "1. Switch to a legacy gas network (e.g., BSC) and initiate a token transfer.", "2. Manually edit gas price and gas limit, submit the transaction, and ensure it confirms.", "3. Verify the confirm screen and activity detail display legacy gas correctly and no 1559 fields are shown.", "4. Ensure retry/speed-up behaves correctly using legacy gas (no base/priority fields)." ], "whyThisMatters": "Incorrect handling of legacy gas can block transactions on popular non-1559 networks, directly impacting user funds." }, { "area": "Assets: Network enablement initialization (Assets/network-enablement-controller-init)", "riskLevel": "high", "testSteps": [ "1. Fresh install 13.54.0 and complete basic onboarding to a new seed.", "2. Visit Assets on Ethereum, then switch to Polygon and Arbitrum; observe asset population timing and behavior.", "3. Toggle any available per-network detection setting (if present) and confirm the asset list updates only for the toggled network.", "4. Reload the extension and confirm settings persist and do not trigger unexpected re-fetches on disabled networks." ], "whyThisMatters": "Initialization changes can cause missing or excessive asset fetches per network, impacting performance and user trust in balances." }, { "area": "NFTs: Detection notice and Import NFTs flow", "riskLevel": "high", "testSteps": [ "1. With NFT detection OFF, open the NFTs tab and choose 'Import NFTs'.", "2. Verify a detection-related notice appears, read-through it, and proceed to manual import with a known contract and token ID.", "3. After successful import, enable NFT detection and ensure the imported NFT is not duplicated after refresh.", "4. Disable NFT detection again and confirm the imported NFT remains visible and stable." ], "whyThisMatters": "New notice/UI around NFT detection can alter the import flow; errors here create duplicates or hide assets." }, { "area": "Account Group Balance: Totals and currency conversion accuracy", "riskLevel": "medium", "testSteps": [ "1. Create at least 3 accounts with different ETH/token balances and ensure fiat conversion is enabled.", "2. Open the home/account overview and note the account-group total balance display.", "3. Switch the primary currency (e.g., from USD to EUR) and verify the group total updates accurately.", "4. Switch networks (Mainnet to a testnet) and confirm the group total reflects only relevant assets for the selected network." ], "whyThisMatters": "A miscalculated group balance undermines user trust and can drive incorrect financial decisions." }, { "area": "Privacy and Analytics: MetaMetrics consent and event gating", "riskLevel": "medium", "testSteps": [ "1. From Settings > Security & Privacy, opt OUT of MetaMetrics and perform common actions (switch networks, open activity).", "2. Confirm no analytics-related prompts or errors occur and that flows work normally.", "3. Opt IN to MetaMetrics and repeat actions; ensure no intrusive prompts and navigation remains smooth.", "4. Lock and unlock the wallet to ensure consent persists across sessions." ], "whyThisMatters": "Analytics adapter changes can inadvertently enable tracking when disabled or destabilize flows guarded by analytics checks." }, { "area": "App State Controller: Lock/Unlock and pending approvals UX", "riskLevel": "medium", "testSteps": [ "1. With an active dapp connection requesting a signature, lock the wallet while the request is pending.", "2. Unlock and confirm the pending approval is restored to the foreground with correct data.", "3. Complete the approval and verify the app returns to the correct route without orphaned state.", "4. Repeat with multiple queued approvals to confirm order and UI focus are correct." ], "whyThisMatters": "App-state changes can cause lost approvals or broken navigation, directly affecting signing and dapp trust." }, { "area": "Assets List Interaction: Search/filter stability", "riskLevel": "medium", "testSteps": [ "1. On a network with many tokens, use the Assets list search to filter by symbol and name.", "2. Add a new custom token that matches the current search; confirm it appears immediately in filtered results.", "3. Clear the search, switch networks, and ensure filters reset properly without stale results.", "4. Reopen the popup and verify the previous network and assets render correctly without lag or empty states." ], "whyThisMatters": "UI changes in the assets list/control bar can introduce subtle state bugs affecting token discoverability." } ] } }