chore(deps-dev): bump baseline-browser-mapping from 2.10.37 to 2.11.21

[dependabot]

Bumps baseline-browser-mapping from 2.10.37 to 2.11.21.

Release notes

Sourced from baseline-browser-mapping's releases.

v2.11.0

What's Changed in 2.11.0

• feat: Adds a new getTimeline() method for getting the series of minimum browser changes, either grouped by date or by browser.
• refactor: Substantial refactoring of the data compression process that replaces the full list of browsers from @mdn/browser-compat-data and downstream-browsers.json and features from web-features (in their very pared down form) with a change-list timeline that reflects which versions supported Baseline (newly available) on a given date. Thanks to @​swwind for the idea!
• refactor: Some common functions have been moved to a util.ts module for use in other scripts.
• fix: Removes process.exit() calls when unsupported option combinations are passed to getCompatibleVersions() and getAllVersions() in favour of throwing an Error. There is a small security risk with process.exit() calls that sites accepting unsanitised inputs could be the subject of attacks. Unsupported config options now throw and Error which should allow for more graceful handling. Thanks to @​bnbdr for flagging this as vulnerability CVE-2026-45819 .

Fixes #134

Full Changelog: web-platform-dx/baseline-browser-mapping@v2.10.44...v2.11.0

Commits

• 0e5ed80 Patch to 2.11.21 because browser or feature data changed
• 11da0b6 Browser or feature data changed
• 69fcc81 Updating static site
• b964de0 Patch to 2.11.20 because browser or feature data changed
• 723099f Browser or feature data changed
• f44163d Updating static site
• 8966043 Patch to 2.11.19 because browser or feature data changed
• e18601d Browser or feature data changed
• 28cb50a Updating static site
• cb33a83 Patch to 2.11.18 because browser or feature data changed
• Additional commits viewable in compare view

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 rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will 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 version will 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 dependency will 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.

[pixelpix13]

Review & testing summary

Rebased this PR onto current development. Updated package.json and package-lock.json only — left yarn.lock unchanged since CI uses npm ci.

What changed

• baseline-browser-mapping: ^2.10.29 → ^2.11.21 (devDependency patch/minor bump)
• No application code changes
• Security fix included:
  • CVE-2026-45819 — removed process.exit() calls in favour of throwing errors for unsupported config options

Local testing

1. Checked out rebased branch from latest development
2. npm ci — installed successfully
3. npm test — 158/158 test suites passed (2,260 tests)

CI status (after rebase)

• Lint Check — (update after push)
• Tests with 10% Coverage Enforcement — (update after push)
• SonarCloud Scan — (update after push)

Risk assessment

• Low risk — devDependency only; not used in runtime application code
• Used for browser compatibility data in build/tooling chain
• No direct imports in src/

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud