Resolve qs security advisories in the documentation dependency graph - #122
Merged
Conversation
Member
Author
|
Merged and deployed from f34e7ea. The GitHub Pages deployment completed successfully: https://github.com/durable-workflow/durable-workflow.github.io/actions/runs/33959019724 . Dependabot alerts 132 and 133 both report fixed at 2026-09-05 09:49:33 UTC. The organization open-alert inventory is empty; the previously recorded image-size exceptions remain separate from this fix. |
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
Select qs 6.16.0 through the existing npm override mechanism and update only its lockfile entry. Express and body-parser constrain their transitive dependency to ~6.15.1, so a lockfile-only update cannot select the patched minor release.
Addresses GHSA-4mjr-xmp4-gh2g and GHSA-x5fp-wj9c-mxmx. The published site is static; this fixes the build/development dependency graph rather than claiming a production application compromise.
Validation
No documentation prose, pipeline, or new guardrail scripts are changed.