Skip to content

chore(deps): update dependency baseline-browser-mapping to ^2.11.20 - #816

Closed
renovate[bot] wants to merge 1 commit into
devfrom
renovate/baseline-browser-mapping-2.x
Closed

chore(deps): update dependency baseline-browser-mapping to ^2.11.20#816
renovate[bot] wants to merge 1 commit into
devfrom
renovate/baseline-browser-mapping-2.x

Conversation

@renovate

@renovate renovate Bot commented Aug 31, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
baseline-browser-mapping ^2.11.18^2.11.20 age confidence

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.


Release Notes

web-platform-dx/baseline-browser-mapping (baseline-browser-mapping)

v2.11.20

Compare Source

v2.11.19

Compare Source

v2.11.18

Compare Source

v2.11.17

Compare Source

v2.11.16

Compare Source

v2.11.15

Compare Source

v2.11.14

Compare Source

v2.11.13

Compare Source

v2.11.12

Compare Source

v2.11.11

Compare Source

v2.11.10

Compare Source

v2.11.9

Compare Source

v2.11.8

Compare Source

v2.11.7

Compare Source

v2.11.6

Compare Source

v2.11.5

Compare Source

v2.11.4

Compare Source

v2.11.3

Compare Source

v2.11.1

Compare Source

v2.11.0

Compare Source

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

v2.10.44

Compare Source

v2.10.43

Compare Source

v2.10.42

Compare Source

v2.10.41

Compare Source

v2.10.40

Compare Source


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate Bot added the dependencies Issues related to dependency updates or management label Aug 31, 2026
@renovate
renovate Bot force-pushed the renovate/baseline-browser-mapping-2.x branch from 170b1f0 to 67c3c6a Compare August 31, 2026 19:02
@renovate

renovate Bot commented Aug 31, 2026

Copy link
Copy Markdown
Contributor Author

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: formulus/package-lock.json
npm warn Unknown env config "store". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options.
npm warn Unknown project config "node-linker". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options.
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: formulus-app@1.3.1
npm error Found: react-native-nitro-modules@0.35.10
npm error node_modules/react-native-nitro-modules
npm error   react-native-nitro-modules@"^0.35.10" from the root project
npm error
npm error Could not resolve dependency:
npm error peer react-native-nitro-modules@">=0.36.5" from react-native-nitro-sound@0.2.19
npm error node_modules/react-native-nitro-sound
npm error   react-native-nitro-sound@"^0.2.19" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry this command with --force or --legacy-peer-deps to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2026-08-31T19_02_26_977Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-08-31T19_02_26_977Z-debug-0.log

@r0ssing r0ssing closed this Sep 1, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Issues related to dependency updates or management

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant