release: 7.74.2

[weitingsun]

🚀 v7.74.2 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

• Mobile Platform

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

---

Note

Low Risk
Low risk: updates a single constant used for displaying/reporting OTA build info, with no runtime logic changes beyond the version string.

Overview
Updates OTA_VERSION in app/constants/ota.ts from the sentinel vX.XX.X to v7.74.2 to reflect the current OTA/native release identifier.

^{Reviewed by Cursor Bugbot for commit bfe928b. 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.

[github-actions]

🔍 Smart E2E Test Selection

• Selected E2E tags: None (no tests recommended)
• Selected Performance tags: None (no tests recommended)
• Risk Level: low
• AI Confidence: 98%

click to see 🤖 AI reasoning details

E2E Test Selection:
The only change is a version string update in app/constants/ota.ts: OTA_VERSION changes from placeholder 'vX.XX.X' to 'v7.74.2'. This is a pure release preparation/version bump change. The OTA_VERSION constant is used only for: (1) displaying version info in Settings > App Information screen, (2) tagging Sentry error reports with the OTA version, and (3) including OTA version in app log metadata. None of these usages affect user flows, business logic, navigation, controllers, or any testable E2E behavior. No E2E tests are warranted for this purely informational metadata change.

Performance Test Selection:
A version string update has zero performance impact. The OTA_VERSION constant is used only for metadata display and logging purposes, with no effect on rendering, data loading, or any performance-sensitive code paths.

View GitHub Actions results