Repository navigation
chore: Update outdated browser warnings - #47451
Conversation
Builds ready [c17d6cc] [reused from 863ca3f]
⚡ Performance Benchmarks (Total: 🟢 0 pass · 🟡 0 warn · 🔴 0 fail)
Bundle Size Diffs
|
c17d6cc to
ed86286
Compare
|
Current version of PR was reviewed by /review-bugbot on Nov 5, 11:27 GMT+1. It flagged 0 findings. Bugbot on commit |
Builds ready [ed86286]
⚡ Performance Benchmarks (Total: 🟢 6 pass · 🟡 3 warn · 🔴 4 fail)
Bundle Size Diffs
|
|



Description
Update outdated browser warnings, the following browser versions will be the minimum in the near future:
137137140121Please note that we are bumping Chrome beyond the regular 2ish years limit to include
ed25519andX25519SubtleCrypto support for improved performance (via@metamask/cryptography).This PR should be followed up with bumps to the actual minimums after one release cycle.
Changelog
CHANGELOG entry: Updated warning for outdated browsers. We will drop support for outdated browsers in the following release.
Note
Low Risk
Threshold and test-only changes for browser deprecation warnings; no auth, crypto, or runtime logic changes beyond who sees the notice.
Overview
Raises the outdated browser warning cutoffs in
OUTDATED_BROWSER_VERSIONSso more users see the in-app notice before hard minimums land next release: Chrome/Edge 137, Firefox 140 (previous ESR), Opera 121 (Chromium 137). Inline comments for Firefox ESR and Opera/Chromium mapping are updated to match.The
#getIsBrowserDeprecatedunit tests now use user-agent strings at/just below those new floors so “modern” vs “outdated” expectations stay aligned.Chrome/Edge are bumped above the usual ~2-year floor to target browsers with ed25519 / X25519 SubtleCrypto (for
@metamask/cryptography); this PR only changes warnings, not enforcement.Reviewed by Cursor Bugbot for commit c17d6cc. Bugbot is set up for automated code reviews on this repo. Configure here.