🚨 [security] Update postcss 8.5.6 → 8.5.10 (patch)#167
Open
depfu[bot] wants to merge 1 commit into
Open
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
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.
🚨 Your current dependencies have known security vulnerabilities 🚨
This dependency update fixes known security vulnerabilities. Please see the details below and assess their impact carefully. We recommend to merge and deploy this as soon as possible!
Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ postcss (8.5.6 → 8.5.10) · Repo · Changelog
Security Advisories 🚨
🚨 PostCSS has XSS via Unescaped </style> in its CSS Stringify Output
Release Notes
8.5.10
8.5.9
8.5.8
8.5.7
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 37 commits:
Release 8.5.10 versionEscape </style> in CSS output (#2074)Update dependencies (#2073)Typo (#2072)Thread model (#2071)Create incident response docs (#2070)Release 8.5.9 versionAvoid RegExp when we can use simple JSMove SECURITY.txt for docs folder to keep GitHub page cleanerCreate SECURITY.mdAnother way to fix CI with .ts ext in tests on old Node.jsAnother way to fix CI with TS on old Node.jsAnother way to fix CI with old Node.jsFix another issue with Node.js 10 on CITry to fix Node.js 10 on CIMove to oxfmtUpdate dependenciesAdd CoC from Slow ReaderUpdate emailRelease 8.5.8 versionRun git hook registerUpdate Processor#versionRelease 8.5.7 versionFix uvu Node.js 25 supportUpdate dependenciesSpeed up source map annotation cleaning by moving from RegExpRemove bannerchore: speed up space-only string check in lib/parser.js (#2064)Update dependenciesAdd Node.js 24 and 25 to CIPin CI actionsAdd new pluginFix typographyUpdate sponsor descriptionAdd Warp bannerdocs: add postcss-inline-extract plugin to plugins list (#2057)docs: added my if() function PostCSS plugin (#2054)Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with
@depfu rebase.All Depfu comment commands
Go to the Depfu Dashboard to see the state of your dependencies and to customize how Depfu works.