-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore(deps): update dependency postcss to v8.4.31 [security] #1232
Open
renovate
wants to merge
1
commit into
master
Choose a base branch
from
renovate/npm-postcss-vulnerability
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains 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
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #1232 +/- ##
=======================================
Coverage 85.80% 85.80%
=======================================
Files 600 600
Lines 13222 13222
Branches 2746 2746
=======================================
Hits 11345 11345
Misses 1812 1812
Partials 65 65 ☔ View full report in Codecov by Sentry. |
renovate
bot
force-pushed
the
renovate/npm-postcss-vulnerability
branch
8 times, most recently
from
May 28, 2024 17:46
de7832c
to
b3afda3
Compare
renovate
bot
force-pushed
the
renovate/npm-postcss-vulnerability
branch
10 times, most recently
from
June 6, 2024 18:45
ac1bd1b
to
5d8d3c0
Compare
renovate
bot
force-pushed
the
renovate/npm-postcss-vulnerability
branch
2 times, most recently
from
June 12, 2024 16:11
b7e4ca4
to
326de70
Compare
renovate
bot
force-pushed
the
renovate/npm-postcss-vulnerability
branch
3 times, most recently
from
June 24, 2024 13:58
67bc539
to
96d6de5
Compare
renovate
bot
force-pushed
the
renovate/npm-postcss-vulnerability
branch
4 times, most recently
from
July 3, 2024 18:57
4170a13
to
6f2fcf0
Compare
renovate
bot
force-pushed
the
renovate/npm-postcss-vulnerability
branch
from
July 8, 2024 16:59
6f2fcf0
to
0ab49f9
Compare
renovate
bot
force-pushed
the
renovate/npm-postcss-vulnerability
branch
3 times, most recently
from
October 9, 2024 09:04
fbae62d
to
afb1e5e
Compare
renovate
bot
force-pushed
the
renovate/npm-postcss-vulnerability
branch
6 times, most recently
from
October 18, 2024 19:34
2623795
to
ab368aa
Compare
renovate
bot
force-pushed
the
renovate/npm-postcss-vulnerability
branch
2 times, most recently
from
October 23, 2024 10:29
21be861
to
86386d3
Compare
renovate
bot
force-pushed
the
renovate/npm-postcss-vulnerability
branch
from
October 30, 2024 14:40
86386d3
to
ba92939
Compare
renovate
bot
force-pushed
the
renovate/npm-postcss-vulnerability
branch
5 times, most recently
from
November 13, 2024 13:27
2d56605
to
dce6702
Compare
renovate
bot
force-pushed
the
renovate/npm-postcss-vulnerability
branch
5 times, most recently
from
November 19, 2024 14:59
cb818fa
to
c559860
Compare
renovate
bot
force-pushed
the
renovate/npm-postcss-vulnerability
branch
4 times, most recently
from
November 26, 2024 16:19
fe5d0c1
to
3740a7c
Compare
renovate
bot
force-pushed
the
renovate/npm-postcss-vulnerability
branch
2 times, most recently
from
December 2, 2024 22:03
7e0e5eb
to
02d16f9
Compare
renovate
bot
force-pushed
the
renovate/npm-postcss-vulnerability
branch
from
December 3, 2024 07:45
02d16f9
to
320a0bb
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
None yet
0 participants
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.
This PR contains the following updates:
8.4.24
->8.4.31
GitHub Vulnerability Alerts
CVE-2023-44270
An issue was discovered in PostCSS before 8.4.31. It affects linters using PostCSS to parse external Cascading Style Sheets (CSS). There may be
\r
discrepancies, as demonstrated by@font-face{ font:(\r/*);}
in a rule.This vulnerability affects linters using PostCSS to parse external untrusted CSS. An attacker can prepare CSS in such a way that it will contains parts parsed by PostCSS as a CSS comment. After processing by PostCSS, it will be included in the PostCSS output in CSS nodes (rules, properties) despite being originally included in a comment.
Release Notes
postcss/postcss (postcss)
v8.4.31
Compare Source
\r
parsing to fix CVE-2023-44270.v8.4.30
Compare Source
v8.4.29
Compare Source
Node#source.offset
(by Ido Rosenthal).v8.4.28
Compare Source
Root.source.end
for better source map (by Romain Menke).Result.root
types whenprocess()
has no parser.v8.4.27
Compare Source
Container
clone methods types.v8.4.26
Compare Source
v8.4.25
Compare Source
Configuration
📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.