build(deps): bump qs and express in /docs - #332
Merged
Conversation
Bumps [qs](https://github.com/ljharb/qs) and [express](https://github.com/expressjs/express). These dependencies needed to be updated together. Updates `qs` from 6.13.0 to 6.14.2 - [Changelog](https://github.com/ljharb/qs/blob/main/CHANGELOG.md) - [Commits](ljharb/qs@v6.13.0...v6.14.2) Updates `express` from 4.21.2 to 4.22.1 - [Release notes](https://github.com/expressjs/express/releases) - [Changelog](https://github.com/expressjs/express/blob/v4.22.1/History.md) - [Commits](expressjs/express@4.21.2...v4.22.1) --- updated-dependencies: - dependency-name: qs dependency-version: 6.14.2 dependency-type: indirect - dependency-name: express dependency-version: 4.22.1 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
2 tasks
Member
|
Superseded by #342 (leaving open until that merges). Partial fix: this brings #342 resolves qs to 6.15.3 and express to 4.22.2. |
glennko
approved these changes
Sep 3, 2026
glennko
left a comment
Member
There was a problem hiding this comment.
Lockfile-only dependency bump; CI green.
glennko
added a commit
that referenced
this pull request
Sep 3, 2026
Single `npm audit fix --package-lock-only` pass on the docs site. package.json is untouched -- no declared range changes, only the resolved tree. Regenerated against current main, which now carries the merged dependabot bumps (#347, #346, #332, #326, #314, #352, #351, #349, #348). Those bumps did not reach either critical, and dependabot never proposed a fix for websocket-driver at all. before after critical 2 0 high 27 18 moderate 14 8 low 5 0 total 48 26 Both criticals cleared: - shell-quote 1.8.3 -> 1.10.0 (CVE-2026-9277) - websocket-driver 0.7.4 -> 0.7.5 (CVE-2026-54466) Also lodash 4.17.23 -> 4.18.1 and node-forge dropped from the tree. The remaining 26 sit inside the Docusaurus dependency tree -- image-size, serialize-javascript, and the webpack-dev-server -> sockjs -> uuid chain. Most report no non-breaking fix and would need a Docusaurus major upgrade. The dev-server chain affects `docusaurus start`, not `docusaurus build`. `npm audit fix --force` was deliberately not used -- it would churn the Docusaurus major version and risk the docs build, for issues that are dev-time only.
glennko
added a commit
that referenced
this pull request
Sep 3, 2026
…342) Single `npm audit fix --package-lock-only` pass on the docs site. package.json is untouched -- no declared range changes, only the resolved tree. Regenerated against current main, which now carries the merged dependabot bumps (#347, #346, #332, #326, #314, #352, #351, #349, #348). Those bumps did not reach either critical, and dependabot never proposed a fix for websocket-driver at all. before after critical 2 0 high 27 18 moderate 14 8 low 5 0 total 48 26 Both criticals cleared: - shell-quote 1.8.3 -> 1.10.0 (CVE-2026-9277) - websocket-driver 0.7.4 -> 0.7.5 (CVE-2026-54466) Also lodash 4.17.23 -> 4.18.1 and node-forge dropped from the tree. The remaining 26 sit inside the Docusaurus dependency tree -- image-size, serialize-javascript, and the webpack-dev-server -> sockjs -> uuid chain. Most report no non-breaking fix and would need a Docusaurus major upgrade. The dev-server chain affects `docusaurus start`, not `docusaurus build`. `npm audit fix --force` was deliberately not used -- it would churn the Docusaurus major version and risk the docs build, for issues that are dev-time only. Co-authored-by: Glenn Ko <glennko@users.noreply.github.com>
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.
Bumps qs and express. These dependencies needed to be updated together.
Updates
qsfrom 6.13.0 to 6.14.2Changelog
Sourced from qs's changelog.
... (truncated)
Commits
bdcf0c7v6.14.2294db90[readme] document thataddQueryPrefixdoes not add?to empty output5c308e5[readme] clarifyparseArraysandarrayLimitdocumentation6addf8c[Fix]parse: mark overflow objects for indexed notation exceedingarrayLimitcfc108f[Fix]arrayLimitmeans max count, not max index, incombine/merge/`pars...febb644[Fix]parse: throw onarrayLimitexceeded with indexed notation when `thr...f6a7abf[Fix]parse: enforcearrayLimitoncomma-parsed valuesfbc5206[Fix]parse: fix error message to reflect arrayLimit as max index; remove e...1b9a8b4[actions] fix rebase workflow permissions2a35775[meta] fix changelog typo (arrayLength→arrayLimit)Updates
expressfrom 4.21.2 to 4.22.1Release notes
Sourced from express's releases.
Changelog
Sourced from express's changelog.
Commits
12fae144.22.15ddf311Revert "sec: security patch for CVE-2024-51999"49744ab4.22.0 (#6921)6e97452sec: security patch for CVE-2024-519996a23d34deps: use tilde notation forqs(#6919)8c12cdfdeps: qs@6.14.0 (#6909)7fea74fdeps: use tilde notation for certain dependencies (#6905)dac7a04chore: wider range for query test skip (#6513)997919bci: add node.js 24 to test matrix (#6506)36fb59cfix(ci): reordernpm isteps to fix ci for older node versions (#6336)You can trigger a rebase of this PR 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.