Skip to content

[Snyk] Upgrade postcss from 8.4.19 to 8.5.3#188

Open
leroyanders wants to merge 1 commit into
masterfrom
snyk-upgrade-36da70b1fa2aabb6fcc30500fb739653
Open

[Snyk] Upgrade postcss from 8.4.19 to 8.5.3#188
leroyanders wants to merge 1 commit into
masterfrom
snyk-upgrade-36da70b1fa2aabb6fcc30500fb739653

Conversation

@leroyanders

Copy link
Copy Markdown
Owner

snyk-top-banner

Snyk has created this PR to upgrade postcss from 8.4.19 to 8.5.3.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.


  • The recommended version is 34 versions ahead of your current version.

  • The recommended version was released a month ago.

Issues fixed by the recommended upgrade:

Issue Score Exploit Maturity
medium severity Improper Input Validation
SNYK-JS-NANOID-8492085
529 No Known Exploit
Release notes
Package name: postcss
  • 8.5.3 - 2025-02-19
  • 8.5.2 - 2025-02-10
  • 8.5.1 - 2025-01-14
    • Fixed backwards compatibility for complex cases (by @ romainmenke).
  • 8.5.0 - 2025-01-13
    President Alloces seal

    PostCSS 8.5 brought API to work better with non-CSS sources like HTML, Vue.js/Svelte sources or CSS-in-JS.

    @ romainmenke during his work on Stylelint added Input#document in additional to Input#css.

    root.source.input.document //=> "<p>Hello</p>
    // <style>
    // p {
    // color: green;
    // }
    // </style>"
    root.source.input.css //=> "p {
    // color: green;
    // }"

    Thanks to Sponsors

    This release was possible thanks to our community.

    If your company wants to support the sustainability of front-end infrastructure or wants to give some love to PostCSS, you can join our supporters by:

  • 8.4.49 - 2024-11-11
  • 8.4.48 - 2024-11-10
    • Fixed position calculation in error/warnings methods (by @ romainmenke).
  • 8.4.47 - 2024-09-14
    • Removed debug code.
  • 8.4.46 - 2024-09-14
    • Fixed Cannot read properties of undefined (reading 'before').
  • 8.4.45 - 2024-09-04
    • Removed unnecessary fix which could lead to infinite loop.
  • 8.4.44 - 2024-09-02
    • Another way to fix markClean is not a function error.
  • 8.4.43 - 2024-09-01
  • 8.4.42 - 2024-08-31
  • 8.4.41 - 2024-08-05
  • 8.4.40 - 2024-07-24
  • 8.4.39 - 2024-06-29
  • 8.4.38 - 2024-03-20
  • 8.4.37 - 2024-03-19
  • 8.4.36 - 2024-03-17
  • 8.4.35 - 2024-02-07
  • 8.4.34 - 2024-02-05
  • 8.4.33 - 2024-01-04
  • 8.4.32 - 2023-12-02
  • 8.4.31 - 2023-09-28
  • 8.4.30 - 2023-09-18
  • 8.4.29 - 2023-08-29
  • 8.4.28 - 2023-08-15
  • 8.4.27 - 2023-07-21
  • 8.4.26 - 2023-07-13
  • 8.4.25 - 2023-07-06
  • 8.4.24 - 2023-05-28
  • 8.4.23 - 2023-04-19
  • 8.4.22 - 2023-04-16
  • 8.4.21 - 2023-01-06
  • 8.4.20 - 2022-12-11
  • 8.4.19 - 2022-11-10
from postcss GitHub release notes

Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • This PR was automatically created by Snyk using the credentials of a real user.
  • Max score is 1000. Note that the real score may have changed since the PR was raised.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

Snyk has created this PR to upgrade postcss from 8.4.19 to 8.5.3.

See this package in npm:
postcss

See this project in Snyk:
https://app.snyk.io/org/leroywagner/project/5cd8e3fb-66fa-4f1c-9223-3ee8e55ea4f3?utm_source=github&utm_medium=referral&page=upgrade-pr
@vercel

vercel Bot commented Mar 20, 2025

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
nessapp ✅ Ready (Inspect) Visit Preview 💬 Add feedback Mar 20, 2025 3:38am

@netlify

netlify Bot commented Mar 20, 2025

Copy link
Copy Markdown

Deploy Preview for voluble-alfajores-7cbeea failed.

Name Link
🔨 Latest commit 0302d7a
🔍 Latest deploy log https://app.netlify.com/sites/voluble-alfajores-7cbeea/deploys/67db8d8514245b0008ea2c98

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants