chore(deps): update dependency postcss to v8.5.3

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
postcss (source)	8.4.31 -> 8.5.3

---

Release Notes

postcss/postcss (postcss)

v8.5.3

Compare Source

• Added more details to Unknown word error (by @​hiepxanh).
• Fixed types (by @​romainmenke).
• Fixed docs (by @​catnipan).

v8.5.2

Compare Source

• Fixed end position of rules with semicolon (by @​romainmenke).

v8.5.1

Compare Source

• Fixed backwards compatibility for complex cases (by @​romainmenke).

v8.5.0: 8.5 “Duke Alloces”

Compare Source

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.

v8.4.49

Compare Source

• Fixed custom syntax without source.offset (by @​romainmenke).

v8.4.48

Compare Source

• Fixed position calculation in error/warnings methods (by @​romainmenke).

v8.4.47

Compare Source

• Removed debug code.

v8.4.46

Compare Source

• Fixed Cannot read properties of undefined (reading 'before').

v8.4.45

Compare Source

• Removed unnecessary fix which could lead to infinite loop.

v8.4.44

Compare Source

• Another way to fix markClean is not a function error.

v8.4.43

Compare Source

• Fixed markClean is not a function error.

v8.4.42

Compare Source

• Fixed CSS syntax error on long minified files (by @​varpstar).

v8.4.41

Compare Source

• Fixed types (by @​nex3 and @​querkmachine).
• Cleaned up RegExps (by @​bluwy).

v8.4.40

Compare Source

• Moved to getter/setter in nodes types to help Sass team (by @​nex3).

v8.4.39

Compare Source

• Fixed CssSyntaxError types (by @​romainmenke).

v8.4.38

Compare Source

• Fixed endIndex: 0 in errors and warnings (by @​romainmenke).

v8.4.37

Compare Source

• Fixed original.column are not numbers error in another case.

v8.4.36

Compare Source

• Fixed original.column are not numbers error on broken previous source map.

v8.4.35

Compare Source

• Avoid ! in node.parent.nodes type.
• Allow to pass undefined to node adding method to simplify types.

v8.4.34

Compare Source

• Fixed AtRule#nodes type (by Tim Weißenfels).
• Cleaned up code (by Dmitry Kirillov).

v8.4.33

Compare Source

• Fixed NoWorkResult behavior difference with normal mode (by Romain Menke).
• Fixed NoWorkResult usage conditions (by @​ahmdammarr).

v8.4.32

Compare Source

• Fixed postcss().process() types (by Andrew Ferreira).

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[cloudflare-workers-and-pages]

Deploying cite with    Cloudflare Pages

Latest commit:	0ef2071
Status:	✅  Deploy successful!
Preview URL:	https://2b588121.cite.pages.dev
Branch Preview URL:	https://renovate-postcss-8-x-lockfil.cite.pages.dev

View logs

[changeset-bot]

⚠️ No Changeset found

Latest commit: 0ef2071

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR