chore(deps): bump browserslist from 4.25.4 to 4.28.9 - #34
Merged
Merged
Conversation
Bumps [browserslist](https://github.com/browserslist/browserslist) from 4.25.4 to 4.28.9. - [Release notes](https://github.com/browserslist/browserslist/releases) - [Changelog](https://github.com/browserslist/browserslist/blob/main/CHANGELOG.md) - [Commits](browserslist/browserslist@4.25.4...4.28.9) --- updated-dependencies: - dependency-name: browserslist dependency-version: 4.28.9 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
joshuanapoli
approved these changes
Sep 6, 2026
joshuanapoli
left a comment
Member
There was a problem hiding this comment.
Summary
Bumps browserslist 4.25.4 -> 4.28.9, resolving GHSA-73wf-gq98-2v4g (high: uncaught crash / prototype write in normalizeStats() when parsing an untrusted browserslist-stats.json). Pulls the accompanying data-package updates (caniuse-lite, electron-to-chromium, node-releases, update-browserslist-db 1.3.2) and the new baseline-browser-mapping dependency. Lockfile/PnP-cache only; no source or manifest changes.
Risks
Low.
- Not exploitable here. The advisory requires browserslist to load a custom
browserslist-stats.json. This repo has nobrowserslistfield inpackage.json, no.browserslistrc, and no stats file, sonormalizeStats()is never reached with attacker-controlled input. The bump is hygiene against a dev-scope alert rather than a live exposure. - Dev-scope and effectively inert.
browserslistis transitive via@babel/helper-compilation-targets@7.29.7-> Babel. Our runtime dependencies are onlyaxiosandcommander, so nothing reaches the shipped CLI. On top of that,jest.config.jstransforms through@swc/jestwith an explicittarget: "es2020", notbabel-jest— so the Babel target-resolution path that would consume browserslist is not in our transform pipeline at all. - Minor-version bump within 4.x; the
browserslist()API is unchanged. The bulk of the diff is refreshed browser-compat data, which only matters to consumers that resolve queries — we have none. - New transitive package
baseline-browser-mapping@2.11.21enters the dev tree. It is a data package (browser baseline tables) required by browserslist 4.28.x, added to the Yarn PnP cache in this diff.
Analysis
- Read the advisory (GHSA-73wf-gq98-2v4g, vulnerable
<= 4.28.6, first patched 4.28.7); 4.28.9 clears it. - Diffed
yarn.lockagainstmain: changes are confined tobrowserslistand its own dependency set, with no unrelated resolution drift and no change tobrace-expansionor other unrelated entries. - Traced reverse dependencies in the lockfile and checked
jest.config.jsandpackage.jsonto confirm dev-only, transitive, and unexercised usage. - Grepped the repo for browserslist configuration to confirm the vulnerable code path is unreachable.
- Rebased the branch onto current
mainfirst, so CI validated this lockfile on top of the already-merged #32 and #33 rather than a stale base. CI (testjob, workflowCI) then passed: it runsyarn install --immutable --immutable-cache— which verifies the lockfile and the PnP zip cache in this diff — followed byprettier --check,eslint .,jest, andtsc.
No mitigating changes were needed.
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Bumps browserslist from 4.25.4 to 4.28.9.
Release notes
Sourced from browserslist's releases.
Changelog
Sourced from browserslist's changelog.
... (truncated)
Commits
12ed525Release 4.28.9 versionb1d8cf9Update dependencies21517b6Improveorparsing performancef2f2e6cRelease 4.28.8 versiond0787c8Update dependenciesfcf8fa9Merge pull request #939 from Jaybhade/fix/baseline-kaios-without-downstream57ecd64fix: support "including kaios" without downstream093a0f6Update EM bannerb637868Release 4.28.7 version313f465Update dependenciesMaintainer changes
This version was pushed to npm by GitHub Actions, a new releaser for browserslist since your current version.
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)You can disable automated security fix PRs for this repo from the Security Alerts page.