Repository navigation
chore(site): upgrade browserslist minimums - #28769
Merged
Merged
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
jeremyruppel
approved these changes
Aug 31, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Update
site/package.jsonbrowserslistfrom Chrome 110 / Firefox 111 / Safari 16.0 (pinned January 2024) to...This is the real floor today. Anything lower is a support claim the CSS will not honor.
browserslistVite (
baseline-widely-available) is already targeting Chrome 111 / Firefox 114 / Safari 16.4 becausevite.config.mtsdoes not overridebuild.target. Tailwind is the stricter constraint: v4 depends on cascade layers,@property, andcolor-mix(), and documents Chrome 111, Safari 16.4, and Firefox 128. Firefox 111 inbrowserslistis the mismatch that matters.Firefox 128 is also the right enterprise pin. It still covers Firefox ESR 140 (supported until mid-October 2026). Current ESR is 153. Do not go above 128 until we are ready to drop ESR 140.
last 2 versionsis a bad query here: Chrome ships every four weeks, so that is only about eight weeks of Chrome.baseline newly availableis too new for locked-down customers.