Repository navigation
chore(site): override postcss-selector-parser to 7.1.6 - #299
Merged
Merged
Conversation
GHSA for postcss-selector-parser (quadratic flat-selector parsing) is fixed only in 7.1.6, and Starlight's expressive-code pins postcss-nested 6, which accepts only 6.x. postcss-nested 7 made the same bump, and the site builds and passes its page checks with the override.
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.
What changed
Resolves Dependabot alert 19 (postcss-selector-parser, quadratic complexity in flat selector parsing). The fix exists only in 7.1.6, and Starlight's expressive-code depends on postcss-nested 6, which accepts only postcss-selector-parser 6.x, so
site/package.jsonoverrides it to 7.1.6. postcss-nested 7 made the same bump upstream.Alert 18 (http-cache-semantics, via Astro) has no patched release. It concerns shared server caches returning another user's response; fanout.run is a statically built site with no such cache, so it is dismissed as tolerable risk rather than changed here.
Verification
npm run buildinsite/, including the table, social-card and canonical checksjust check(pre-push)