fix(deps): security bumps for 2 Dependabot alerts#261
Open
rtBot wants to merge 1 commit into
Open
Conversation
Contributor
There was a problem hiding this comment.
Copilot wasn't able to review any files in this pull request.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
justlevine
approved these changes
Jun 30, 2026
justlevine
left a comment
justlevine
left a comment
Collaborator
There was a problem hiding this comment.
I'm unclear exactly how these changes were made when an npm audit fix fails to address them and dependabot fills.
Tested locally by confirming that nvm use && npm ci don't fail or create lockfile changes. That combined with the existing CI should count.
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.
Summary
Lockfile-only security bumps for transitive dependencies. No source or manifest changes, no major-version bumps.
No CRITICAL alerts in this set.
Why
http-proxy-middleware (patch 2.0.10) and webpack-dev-server (patch 5.2.5) stay within the same major as installed and resolve cleanly via
npm update --package-lock-only. (uuid root incidentally moved 14.0.0 → 14.0.1, both already above the vulnerable range.)How tested
Lockfile-only. NOT built or tested locally (disk-discipline constraint).
package-lock.jsonvalidated as parseable JSON. Rely on CI to confirm.Residual risk / not-applicable (could NOT be safely fixed)
All remaining alerted packages are transitive copies pinned by parents such that the patched version would require a MAJOR bump of the parent (out of scope), or have no patch:
Searchhandling #90 @babel/core (low) — root copy is already 7.29.7 (patched). Two nested copies remain at 7.25.7, pinned exactly by@wordpress/babel-preset-default@7.25.7and@wordpress/scripts@7.25.7. Bumping requires a major @wordpress/* upgrade. FLAGGED.@wordpress/componentsrequires^9.0.1) and uuid@8.3.2 (sockjsrequires^8.3.2) remain; patch 11.1.1 is a MAJOR bump outside both parent ranges. FLAGGED.markdownlint@12.3.2. Patch 14.2.0 is a MAJOR bump (12 → 14). FLAGGED.These require either upstream @wordpress/* major upgrades or maintainer fixes; left for a dedicated follow-up. Do not merge without CI review.