Repository navigation
Update vulnerable docs dependencies - #47
Merged
Merged
Conversation
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
1 participant
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.
Dependabot could not resolve the patched docs dependencies. Update source-map-js to 1.2.2 and http-cache-semantics to 4.3.0, and override postcss-selector-parser to ^7.1.6 because Expressive Code still pulls in its vulnerable 6.x line. The http-cache-semantics release is outside the advisory's affected range; its maintainer disputes the max-stale report.
The frozen-lockfile install, dependency audit, WebAssembly publish, and full docs build pass. Generated code-block base and theme CSS is byte-identical with the new parser.