Repository navigation
chore: Bump minimum supported browsers - #47531
Conversation
Builds ready [a77a043]
⚡ Performance Benchmarks (Total: 🟢 7 pass · 🟡 3 warn · 🔴 2 fail)
Bundle Size Diffs
|
c17d6cc to
ed86286
Compare
a77a043 to
d60fcb5
Compare
Builds ready [d60fcb5]
⚡ Performance Benchmarks (Total: 🟢 9 pass · 🟡 1 warn · 🔴 3 fail)
Bundle Size Diffs
|
d60fcb5 to
259126e
Compare
Builds ready [259126e]
⚡ Performance Benchmarks (Total: 🟢 9 pass · 🟡 0 warn · 🔴 4 fail)
Bundle Size Diffs
|
|
gauthierpetetin
left a comment
There was a problem hiding this comment.
There are still two occurences of Chrome version 123 in docs/sidepanel-implementation.md file. Other than that LGTM
I assumed we wanted to keep that since it just documents when the sidepanel is supported? 🤔 |
gauthierpetetin
left a comment
There was a problem hiding this comment.
I'm not sure how to interpret the versions indicated in docs/sidepanel-implementation.md file.
- On the one hand I agree with you that it seems to indicate the version when the sidepanel is supported.
- On the other hand, the
docs/sidepanel-implementation.mdfile mentions the Chrome version is "specified byminimum_chrome_version" which makes me think we're talking about the version supported by MetaMask.
Also the file indicates Chrome 123+ as version when the sidepanel is supported, although based on this page, sidepanel was supported in Chrome 114+.
Anyways, I don't want to block this PR because of to the documentation, as it's a different discussion.



Description
Following the merge of #47451 and the RC cut we can bump the minimum browser versions to match the values chosen in that PR.
Changelog
CHANGELOG entry: Chrome <137 and Firefox <140 is no longer supported.
Related issues
https://consensyssoftware.atlassian.net/browse/WPC-1538
Note
Low Risk
Config-only version bumps with no runtime logic changes; main impact is dropping support for older Chrome/Firefox versions.
Overview
Raises the minimum supported browser versions to Chrome 137 and Firefox 140 everywhere build and store metadata are defined.
.browserslistrc and babel.config.js compilation targets are aligned with the new floors. Chrome MV2/MV3 manifests set
minimum_chrome_versionto 137; Firefox MV2/MV3 manifests set geckostrict_min_versionto 140.0. Users on older browsers will no longer be able to install or run the extension per the updated manifests and changelog.Reviewed by Cursor Bugbot for commit 259126e. Bugbot is set up for automated code reviews on this repo. Configure here.