Repository navigation
chore(deps): bump xmldom, browserslist, fast-uri, js-yaml in package lockfiles - #154
Merged
Merged
Conversation
…lockfiles npm audit fix (no --force) in package/. Dev-only transitive deps move within their major; package.json is unchanged.
ethanpschoen
marked this pull request as ready for review
September 25, 2026 17:13
jboileau99
approved these changes
Sep 25, 2026
2 of 8 tasks
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.
Description of this change
Patch/minor bumps of dev-only transitive dependencies in
package/, made withnpm audit fix(no--force):No
package.jsonchanges and no major version changes. None of these packages ship in the published tarball, because the package has no runtime dependencies.npm updated
package/yarn.lockin step withpackage-lock.json. CI and release install only frompackage-lock.json, so the checks below say nothing about theyarn.lockchanges.Not included: the 9 alerts on
example/yarn.lock. The example app is never built by CI or published.Why is this change being made?
How was this tested? How can the reviewer verify your testing?
I replayed the CI build job locally in
package/on Node 23.11.0, first on clean main and then on this branch. The job runsnpm ci,prepare,lint,typecheck, jest,npm run all, and thenpm pack --dry-runtarball check.jest --jsonreports 121 passed, 5 skipped, 0 failed (126 total) on both, the same as CI on main.Node 20 and 22 weren't run locally; CI's matrix covers them. Required status checks aren't enforced on main and auto-merge is enabled, so please confirm the Build job is green before merging.
Related issues
Closes Dependabot alerts #434, #436, #438, #439, #440, #441, #443, #444, #445, #446, #447, #448, #451, #452, #454, #456, #457, #458, #459, #460, #461, #462, #463, #464, #465, #466, #467, #468, #471, #473, #474, #475.
Checklist
Note
Low Risk
Lockfile-only patch/minor dev dependency updates with no application code or published package dependency changes.
Overview
Refreshes dev-only transitive dependency versions in
package/package-lock.jsonandpackage/yarn.lockvianpm audit fix, with no changes topackage.jsonor published runtime deps.Browserslist stack is consolidated and bumped:
browserslistmoves to 4.29.1, addsbaseline-browser-mapping, and updatescaniuse-lite,electron-to-chromium,node-releases, andupdate-browserslist-db(duplicate nested copies undercore-js-compatare removed). Patch bumps elsewhere:@xmldom/xmldom0.8.15,fast-uri3.1.8,js-yaml3.15.2 / 4.3.2.CI/release installs from
package-lock.jsononly; the yarn lock stays in sync for local workflows.Reviewed by Cursor Bugbot for commit 30c7181. Configure here.