release: 7.82.0 (#31598)

# 🚀 v7.82.0 Testing & Release Quality Process

Hi Team,
As part of our new **MetaMask Release Quality Process**, here’s a quick
overview of the key processes, testing strategies, and milestones to
ensure a smooth and high-quality deployment.

---

## 📋 Key Processes

### Testing Strategy
- **Developer Teams:**
Conduct regression and exploratory testing for your functional areas,
including automated and manual tests for critical workflows.
- **QA Team:**
Focus on exploratory testing across the wallet, prioritize high-impact
areas, and triage any Sentry errors found during testing.
- **Customer Success Team:**
Validate new functionalities and provide feedback to support release
monitoring.

### GitHub Signoff
- Each team must **sign off on the Release Candidate (RC)** via GitHub
by the end of the validation timeline (**Tuesday EOD PT**).
- Ensure all tests outlined in the Testing Plan are executed, and any
identified issues are addressed.

### Issue Resolution
- **Resolve all Release Blockers** (Sev0 and Sev1) by **Tuesday EOD
PT**.
- For unresolved blockers, PRs may be reverted, or feature flags
disabled to maintain release quality and timelines.

### Cherry-Picking Criteria
- Only **critical fixes** meeting outlined criteria will be
cherry-picked.
- Developers must ensure these fixes are thoroughly reviewed, tested,
and merged by **Tuesday EOD PT**.

---

## 🗓️ Timeline and Milestones

1. **Today (Friday):** Begin Release Candidate validation.
2. **Tuesday EOD PT:** Finalize RC with all fixes and cherry-picks.
3. **Wednesday:** Buffer day for final checks.
4. **Thursday:** Submit release to app stores and begin rollout to 1% of
users.
5. **Monday:** Scale deployment to 10%.
6. **Tuesday:** Full rollout to 100%.

---

## ✅ Signoff Checklist

Each team is responsible for signing off via GitHub. Use the checkbox
below to track signoff completion:

# Team sign-off checklist
- [x] Accounts
- [x] Assets
- [x] Bots Team
- [x] Card
- [x] Confirmations
- [x] Core Platform
- [x] Delegation
- [x] Design System
- [x] Earn
- [x] Engagement
- [x] Mobile Platform
- [x] Mobile UX
- [X] Money Movement
- [x] Networks
- [x] Onboarding
- [x] Perps
- [x] Predict
- [x] Rewards
- [x] Social & AI
- [x] Swaps and Bridge
- [x] Wallet Integrations

This process is a major step forward in ensuring release stability and
quality. Let’s stay aligned and make this release a success! 🚀

Feel free to reach out if you have questions or need clarification.

Many thanks in advance

# Reference
- Testing plan sheet -
https://docs.google.com/spreadsheets/d/1tsoodlAlyvEUpkkcNcbZ4PM9HuC9cEM80RZeoVv5OCQ/edit?gid=404070372#gid=404070372

Author: tommasini

.github/CODEOWNERS

@@ -264,7 +264,6 @@ app/components/UI/CollectibleContractOverview @MetaMask/metamask-assets
 app/components/UI/CollectibleContracts @MetaMask/metamask-assets
 app/components/UI/CollectibleDetectionModal @MetaMask/metamask-assets
 app/components/UI/CollectibleMedia @MetaMask/metamask-assets
-app/components/UI/CollectibleModal @MetaMask/metamask-assets
 app/components/UI/CollectibleOverview @MetaMask/metamask-assets
 app/components/UI/ConfirmAddAsset @MetaMask/metamask-assets
 app/components/UI/DeFiPositions @MetaMask/metamask-assets
@@ -375,6 +374,10 @@ tests/websocket/                                                @MetaMask/qa
 .github/actions/smart-e2e-selection/                            @MetaMask/qa
 .github/workflows/ai-pr-risk-analysis.yml                       @MetaMask/qa
 .github/workflows/auto-label-not-ready-for-e2e.yml              @MetaMask/qa
+.github/workflows/run-appium-e2e-workflow.yml                   @MetaMask/qa
+.github/workflows/run-appium-smoke-tests-android.yml            @MetaMask/qa
+.github/workflows/run-appium-smoke-tests-ios.yml                @MetaMask/qa
+.github/workflows/prebuild-wda-ios.yml                          @MetaMask/qa
 .github/workflows/run-e2e-workflow.yml                          @MetaMask/qa
 .github/workflows/run-e2e-api-specs.yml                         @MetaMask/qa
 .github/workflows/run-e2e-regression-tests-android.yml          @MetaMask/qa

.github/CONTRIBUTING.md

@@ -11,6 +11,7 @@ There are also plenty of open issues we'd love help with. Search the [`good firs
 If you're picking up a bounty or an existing issue, feel free to ask clarifying questions on the issue as you go about your work.
 
 ### Submitting a pull request
+
 When you're done with your project / bugfix / feature and ready to submit a PR, there are a couple guidelines we ask you to follow:
 
 - [ ] **Make sure you followed our [`coding guidelines`](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/CODING_GUIDELINES.md)**: These guidelines aim to maintain consistency and readability across the codebase. They help ensure that the code is easy to understand, maintain, and modify, which is particularly important when working with multiple contributors.
@@ -25,6 +26,6 @@ When you're done with your project / bugfix / feature and ready to submit a PR,
 
 ### Shadow CI jobs
 
-CI jobs prefixed with `[shadow]` (e.g., from `ci-namespace-shadow.yml`) are **advisory only** and never gate merge. They run the same test suite on Namespace runners for performance benchmarking. If a shadow job fails, it does not indicate a problem with your PR -- it reflects the state of the Namespace runner migration trial.
+The Namespace shadow CI (`ci-namespace-shadow.yml`) no longer runs automatically: its automatic triggers (PRs, pushes to `main`, hourly schedule) are disabled now that the Phase 5d benchmark is complete. It is retained for on-demand runs via manual `workflow_dispatch`, or you can dispatch `ci.yml` directly with `runner_provider=namespace`. Any `[shadow]`-prefixed jobs were always **advisory only** and never gated merge.
 
 And that's it! Thanks for helping out.

.github/actions/setup-e2e-env/action.yml

@@ -109,6 +109,12 @@ inputs:
       — Detox does not require the Pods directory to run tests.
     required: false
     default: 'false'
+  install-applesimutils:
+    description: >-
+      Whether to install applesimutils (iOS only). Required by Detox but not
+      by Appium — set to 'false' for Appium test jobs
+    required: false
+    default: 'true'
 
 runs:
   using: 'composite'
@@ -176,7 +182,9 @@ runs:
       run: |
         set -euo pipefail
         sudo mkdir -p "$CACHE_PATH" /opt/android-sdk/.temp
-        sudo chown -R "$(id -u):$(id -g)" "$CACHE_PATH" /opt/android-sdk/.temp
+        # chown the parent dir too so sdkmanager can create x86_64.backup
+        # next to x86_64 during installation (requires write on the parent).
+        sudo chown -R "$(id -u):$(id -g)" "$(dirname "$CACHE_PATH")" /opt/android-sdk/.temp
       shell: bash
 
     # Restore exact system image from cache (GitHub only — Namespace uses nscloud-cache-action in callers)
@@ -444,7 +452,7 @@ runs:
         COCOAPODS_DISABLE_STATS: 'true'
 
     - name: Install applesimutils
-      if: ${{ inputs.platform == 'ios' }}
+      if: ${{ inputs.platform == 'ios' && inputs.install-applesimutils == 'true' }}
       run: |
         if ! brew list applesimutils &>/dev/null; then
           brew tap wix/brew
@@ -455,6 +463,6 @@ runs:
       shell: bash
 
     - name: Check simutils
-      if: ${{ inputs.platform == 'ios' }}
+      if: ${{ inputs.platform == 'ios' && inputs.install-applesimutils == 'true' }}
       run: xcrun simctl list devices
       shell: bash

.github/actions/smart-e2e-selection/action.yml

@@ -38,8 +38,11 @@ outputs:
     description: 'AI confidence score (0-100)'
     value: ${{ steps.final-outputs.outputs.ai_confidence }}
   ai_performance_test_tags:
-    description: 'Performance test tags to run (JSON array format, empty [] means no performance tests)'
+    description: "Performance test tags to run. Empty string '' = run all (conservative fallback). Literal '[]' = skip (AI found no relevant changes). '[\"@Tag\",...]' = run specific tags."
     value: ${{ steps.final-outputs.outputs.ai_performance_test_tags }}
+  ai_performance_test_reasoning:
+    description: 'Reasoning for the performance test selection'
+    value: ${{ steps.final-outputs.outputs.ai_performance_test_reasoning }}
 
 runs:
   using: 'composite'
@@ -134,18 +137,27 @@ runs:
       run: |
         echo "ai_e2e_test_tags=[\"ALL\"]" >> "$GITHUB_OUTPUT"
         echo "ai_confidence=0" >> "$GITHUB_OUTPUT"
-        echo "ai_performance_test_tags=[]" >> "$GITHUB_OUTPUT"
+        # Empty string = run all performance tests (conservative fallback).
+        # '[]' is reserved for "AI ran successfully and found no relevant changes".
+        echo "ai_performance_test_tags=" >> "$GITHUB_OUTPUT"
 
         if [[ "${{ steps.check-skip-label.outputs.SKIP }}" == "true" ]]; then
           echo "⏭️ Skipping AI analysis - skip-smart-e2e-selection label found"
           echo "SKIPPED=true" >> "$GITHUB_OUTPUT"
           echo "SKIP_REASON=skip-smart-e2e-selection label found" >> "$GITHUB_OUTPUT"
           echo "ai_confidence=100" >> "$GITHUB_OUTPUT"
+          # Skip label → run all E2E (ALL) but do NOT launch the PR performance workflow.
+          # Performance tests are expensive and the skip label only opts out of AI selection,
+          # not into a full performance run. Use '[]' so run-performance-tests-pr is skipped.
+          echo "ai_performance_test_tags=[]" >> "$GITHUB_OUTPUT"
         elif [[ "${{ steps.check-release-target.outputs.SKIP }}" == "true" ]]; then
           echo "⏭️ Skipping AI analysis - PR targets a release or stable branch"
           echo "SKIPPED=true" >> "$GITHUB_OUTPUT"
           echo "SKIP_REASON=PR targets a release or stable branch (release/* or stable)" >> "$GITHUB_OUTPUT"
           echo "ai_confidence=100" >> "$GITHUB_OUTPUT"
+          # Release/stable target → the scheduled performance workflow covers these branches.
+          # No need to also trigger the PR performance job.
+          echo "ai_performance_test_tags=[]" >> "$GITHUB_OUTPUT"
         else
           echo "✅ Running AI analysis for PR #$PR_NUMBER"
           # The script will generate the GH output variables - don't fail if script errors
@@ -156,31 +168,39 @@ runs:
       id: final-outputs
       if: always()
       shell: bash
+      env:
+        AI_E2E_TAGS: ${{ steps.ai-analysis.outputs.ai_e2e_test_tags }}
+        AI_CONFIDENCE: ${{ steps.ai-analysis.outputs.ai_confidence }}
+        AI_PERF_TAGS: ${{ steps.ai-analysis.outputs.ai_performance_test_tags }}
+        AI_PERF_REASONING: ${{ steps.ai-analysis.outputs.ai_performance_test_reasoning }}
       run: |
-        TAGS='${{ steps.ai-analysis.outputs.ai_e2e_test_tags }}'
-        if [[ -n "$TAGS" ]]; then
-          printf 'ai_e2e_test_tags=%s\n' "$TAGS" >> "$GITHUB_OUTPUT"
+        if [[ -n "$AI_E2E_TAGS" ]]; then
+          printf 'ai_e2e_test_tags=%s\n' "$AI_E2E_TAGS" >> "$GITHUB_OUTPUT"
         else
           echo 'ai_e2e_test_tags=["ALL"]' >> "$GITHUB_OUTPUT"
         fi
-        echo "ai_confidence=${{ steps.ai-analysis.outputs.ai_confidence }}" >> "$GITHUB_OUTPUT"
-        # Performance test tags (empty array means no performance tests)
-        PERF_TAGS='${{ steps.ai-analysis.outputs.ai_performance_test_tags }}'
-        if [[ -n "$PERF_TAGS" ]]; then
-          printf 'ai_performance_test_tags=%s\n' "$PERF_TAGS" >> "$GITHUB_OUTPUT"
-        else
-          echo 'ai_performance_test_tags=[]' >> "$GITHUB_OUTPUT"
-        fi
+        printf 'ai_confidence=%s\n' "$AI_CONFIDENCE" >> "$GITHUB_OUTPUT"
+        # Performance test tags: empty string = run all (fallback); '[]' = skip (AI found no changes)
+        printf 'ai_performance_test_tags=%s\n' "$AI_PERF_TAGS" >> "$GITHUB_OUTPUT"
+        # Performance test reasoning (multi-line — must use heredoc format)
+        {
+          echo 'ai_performance_test_reasoning<<GHEOF'
+          echo "$AI_PERF_REASONING"
+          echo 'GHEOF'
+        } >> "$GITHUB_OUTPUT"
 
     - name: Display AI Analysis Outputs
       if: always()
       shell: bash
+      env:
+        PERF_REASONING: ${{ steps.final-outputs.outputs.ai_performance_test_reasoning }}
       run: |
         echo "📊 Final GitHub Action Outputs:"
         echo "================================"
         echo "ai_e2e_test_tags: ${{ steps.final-outputs.outputs.ai_e2e_test_tags }}"
         echo "ai_confidence: ${{ steps.final-outputs.outputs.ai_confidence }}"
         echo "ai_performance_test_tags: ${{ steps.final-outputs.outputs.ai_performance_test_tags }}"
+        echo "ai_performance_test_reasoning: $PERF_REASONING"
         echo "================================"
 
     - name: Delete previous comments

.github/guidelines/LABELING_GUIDELINES.md

@@ -39,6 +39,10 @@ Using any of these labels should be exceptional in case of CI friction and urgen
 
 - **skip-smart-e2e-selection**: Bypasses the AI-powered Smart E2E Selection so that the full E2E test suite runs instead of an AI-picked subset. This label does **not** force E2E builds/tests to run on a PR that would otherwise skip them (e.g. docs-only changes). Whether E2E runs at all is determined by path filters, branch, and other skip labels — not this label.
 
+### Force Performance Tests
+
+- **run-performance-tests**: Forces the PR performance E2E workflow to run (all performance tests on Android low-profile devices), even when Smart E2E Selection would skip them (e.g. no performance-relevant changes detected, `skip-e2e`, or `pr-not-ready-for-e2e`). Adding or removing this label re-triggers CI. Not honored on fork PRs.
+
 ### Block merge if any is present
 
 - **needs-qa**: The PR requires a full manual QA prior to being merged and added to a release.

.github/pull-request-template.md

@@ -19,7 +19,10 @@ markdown and must NOT be removed or edited without updating the validator regist
   type=manual-testing Section must have real testing steps or an explicit N/A.
   type=screenshot     Section must have evidence (image/URL) or an explicit N/A.
   type=checklist      Section must have all checkboxes consciously checked.
-  required=true|false Whether a missing/invalid section blocks the PR check.
+  required=true|false Whether a missing/invalid section runs the validator at all.
+  blocking=true|false Whether a failure of this check fails the CI workflow.
+                      Default: false — failures are shown as warnings in the sticky
+                      comment but do not block the PR.
 
 Sections without a directive are checked for structural presence only.
 -->
@@ -36,7 +39,7 @@ Write a short description of the changes included in this pull request, also inc
 
 ## **Changelog**
 
-<!-- mms-check: type=changelog required=true -->
+<!-- mms-check: type=changelog required=true blocking=true -->
 
 <!--
 If this PR is not End-User-Facing and should not show up in the CHANGELOG, you can choose to either: