build(deps): bump qs from 6.15.2 to 6.16.0 - #2653
Conversation
There was a problem hiding this comment.
🟡 Changes recommended
The lockfile does not appear to record the new overrides metadata, which can cause npm ci to fail due to a package.json/package-lock mismatch.
Once you've addressed the issues Copilot identified, you can request another Copilot review.
Pull request overview
Pins the transitive qs dependency to 6.16.0 via npm overrides to address the referenced CVEs without changing the Express 4.x dependency, and updates the lockfile’s resolved versions accordingly.
Changes:
- Add an npm
overridesrule inpackage.jsonto forceqs@6.16.0. - Update
package-lock.jsonentries soqs(and related transitive packages) resolve to the newer versions.
File summaries
| File | Description |
|---|---|
| package.json | Adds an npm overrides entry to pin qs to 6.16.0. |
| package-lock.json | Updates resolved qs and related transitive dependency versions/integrity hashes. |
Review details
- Files reviewed: 1/2 changed files
- Comments generated: 0
- Review effort level: Lite
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Resolves CVE-2026-82417 and CVE-2026-82562 by pinning qs to 6.16.0 while keeping Express 4.x unchanged.
a395669 to
987e1f3
Compare
There was a problem hiding this comment.
🟡 Changes recommended
The new override uses a semver range (^6.16.0) despite the PR stating it is “pinning” to 6.16.0, which can lead to unintended future upgrades when regenerating the lockfile.
Once you've addressed the issues Copilot identified, you can request another Copilot review.
Review details
- Files reviewed: 1/2 changed files
- Comments generated: 1
- Review effort level: Lite
Resolves CVE-2026-82417 and CVE-2026-82562 by pinning qs to 6.16.0 while keeping Express 4.x unchanged.
PR Checklist
What are you changing?
Anything the reviewer should know when reviewing this PR?
If the there are associated PRs in other repositories, please link them here (i.e. device-management-toolkit/repo#365 )