[Snyk] Upgrade postcss from 8.4.39 to 8.5.4

[nerdy-tech-com-gitub]

Snyk has created this PR to upgrade postcss from 8.4.39 to 8.5.4.

ℹ️ 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 15 versions ahead of your current version.

• The recommended version was released a month ago.

Issues fixed by the recommended upgrade:

	Issue	Score	Exploit Maturity
	Regular Expression Denial of Service (ReDoS) SNYK-JS-CROSSSPAWN-8303230	57	Proof of Concept
	Inefficient Regular Expression Complexity SNYK-JS-MICROMATCH-6838728	57	No Known Exploit
	Improper Input Validation SNYK-JS-NANOID-8492085	57	No Known Exploit
	Regular Expression Denial of Service (ReDoS) SNYK-JS-BRACEEXPANSION-9789073	57	Proof of Concept

Release notes

Package name: postcss

• 8.5.4 - 2025-05-29
  
  • Fixed Parcel compatibility issue (by @ git-sumitchaudhary).
• 8.5.3 - 2025-02-19
  
  • Added more details to Unknown word error (by @ hiepxanh).
  • Fixed types (by @ romainmenke).
  • Fixed docs (by @ catnipan).
• 8.5.2 - 2025-02-10
  
  • Fixed end position of rules with semicolon (by @ romainmenke).
• 8.5.1 - 2025-01-14
  
  • Fixed backwards compatibility for complex cases (by @ romainmenke).
• 8.5.0 - 2025-01-13
  

  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:

  • Tidelift with a Spotify-like subscription model supporting all projects from your lock file.
  • Direct donations at GitHub Sponsors or Open Collective.
• 8.4.49 - 2024-11-11
  
  • Fixed custom syntax without source.offset (by @ romainmenke).
• 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
• 8.4.45 - 2024-09-04
• 8.4.44 - 2024-09-02
• 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

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:

• 🧐 View latest project report
• 📜 Customise PR templates
• 🛠 Adjust upgrade PR settings
• 🔕 Ignore this dependency or unsubscribe from future upgrade PRs

Summary by Sourcery

Upgrade the project’s PostCSS dependency to v8.5.4 to resolve known vulnerabilities and incorporate compatibility improvements.

Bug Fixes:

• Address multiple security issues in PostCSS sub-dependencies, including ReDoS and inefficient regex vulnerabilities in cross-spawn, micromatch, nanoid, and brace-expansion.

Enhancements:

• Upgrade PostCSS from version 8.4.x to 8.5.4 to include Parcel compatibility fixes and enhanced non-CSS input support.

[sourcery-ai]

Reviewer's Guide

This PR upgrades the project’s PostCSS dependency from version 8.4.33 to 8.5.4 by updating the version specifier in package.json, ensuring the inclusion of the latest security and bug-fix releases.

Class diagram for updated PostCSS Input API (8.5.x)

classDiagram
  class Input {
    +string css
    +string document
  }
  class Source {
    +Input input
  }
  class Root {
    +Source source
  }
  Root --> Source : has
  Source --> Input : has
  %% New in 8.5.x: Input#document property added alongside Input#css

Loading

File-Level Changes

Change	Details	Files
Bump PostCSS dependency version	Updated the version specifier for postcss in package.json from ^8.4.33 to ^8.5.4	package.json

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.