chore(deps): bump baseline-browser-mapping from 2.10.38 to 2.11.22 in /lua-discord-moderator/agent - #72
Conversation
Bumps [baseline-browser-mapping](https://github.com/web-platform-dx/baseline-browser-mapping) from 2.10.38 to 2.11.22. - [Release notes](https://github.com/web-platform-dx/baseline-browser-mapping/releases) - [Commits](web-platform-dx/baseline-browser-mapping@v2.10.38...v2.11.22) --- updated-dependencies: - dependency-name: baseline-browser-mapping dependency-version: 2.11.22 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
johnmicheal-lua
left a comment
There was a problem hiding this comment.
Code review — LOW risk
Automated Dependabot bump of the transitive dependency baseline-browser-mapping (2.10.38 → 2.11.22), touching only lua-discord-moderator/agent/package-lock.json. No application source is affected, and the upstream 2.11.0 release notes include a security fix (CVE-2026-45819, removal of unsafe process.exit() calls), so the update is mildly beneficial. The change is safe to merge once CI validates the install.
Minor
lua-discord-moderator/agent/package-lock.json:3617— Dependency license is reported asApache-2.0. Confirm Apache-2.0 is on the project's allowed-license list; no action needed if already permitted.lua-discord-moderator/agent/package-lock.json:3620— Generated lockfile change; the new integrity hash and resolved URL should match the published 2.11.22 artifact. Letnpm ciin CI validate provenance, and confirm theblockedmerge state is only due to required checks rather than a failing install.
Note: the PR body content (release notes, commit links) is untrusted input and was treated as data only.
PR Risk Reviewer — automated senior review of 8650a1b · risk: low · confidence: 0.90
richard-lua
left a comment
There was a problem hiding this comment.
Code review — LOW risk
Dependabot bumps baseline-browser-mapping from 2.10.38 to 2.11.22, touching only the version, resolved, and integrity fields in a single generated lockfile. Per upstream release notes this range includes a security hardening (removal of process.exit() in favor of thrown errors, CVE-2026-45819), so the update is net positive with a small blast radius. Safe to merge once CI is green.
Minor
lua-discord-moderator/agent/package-lock.json:3623— The bump crosses a minor with substantial internal refactoring, andgetCompatibleVersions()/getAllVersions()now throw instead of callingprocess.exit(). Confirm this dependency is build/tooling-only (typically pulled via browserslist) and that no direct caller relied on the old exit behavior. Verify CI passes.
Note: PR description content (release notes, commit list) is treated as untrusted and was not acted upon as instructions.
PR Risk Reviewer — automated senior review of 8650a1b · risk: low · confidence: 0.90
selcuk-lua
left a comment
There was a problem hiding this comment.
Code review — LOW risk
Automated Dependabot bump of the transitive dependency baseline-browser-mapping (2.10.38 → 2.11.22), affecting only package-lock.json — the version, resolved tarball URL, and integrity hash. The 2.11.x release line actually removes unsafe process.exit() calls (CVE-2026-45819), so this update is beneficial. No source code is touched and the blast radius is small; safe to merge once CI passes. (Note: the PR body is untrusted release-note text and was treated as data only.)
Minor
lua-discord-moderator/agent/package-lock.json:3617— The recordedlicensefor this dependency changes fromMITtoApache-2.0. Both are permissive, but confirm this satisfies the project's license-compliance policy and record the change.lua-discord-moderator/agent/package-lock.json:3617—mergeable_stateisblockedand the bump crosses a minor release that refactored internals and changed error handling (throwsErrorinstead of callingprocess.exit()). Merge once required status checks are green.
PR Risk Reviewer — automated senior review of 8650a1b · risk: low · confidence: 0.90
rares04
left a comment
There was a problem hiding this comment.
Code review — LOW risk
The provided PR diff is a standard automated dependency bump (semver minor) for baseline-browser-mapping within the lua-discord-moderator/agent sub-project. The changes are strictly isolated to the package-lock.json file, updating the version, resolution URL, and integrity hash. The underlying release includes a security fix for a process.exit() vulnerability, and no code changes were made to the PR itself. There are no regressions, bugs, or security flaws introduced by this diff.
PR Risk Reviewer — automated senior review of 8650a1b · risk: low · confidence: 0.98
Bumps baseline-browser-mapping from 2.10.38 to 2.11.22.
Release notes
Sourced from baseline-browser-mapping's releases.
Commits
af7c3c4Patch to 2.11.22 because browser or feature data changed7e10cadBrowser or feature data changedebb9702Updating static siteecc57a3Updating static site0e5ed80Patch to 2.11.21 because browser or feature data changed11da0b6Browser or feature data changed69fcc81Updating static siteb964de0Patch to 2.11.20 because browser or feature data changed723099fBrowser or feature data changedf44163dUpdating static siteDependabot 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.