Skip to content

Bump postcss from 8.5.15 to 8.5.33 - #528

Open
dependabot[bot] wants to merge 1 commit into
masterfrom
dependabot/npm_and_yarn/postcss-8.5.25
Open

dependabot[bot] wants to merge 1 commit into
masterfrom
dependabot/npm_and_yarn/postcss-8.5.25

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Aug 1, 2026 •

Copy link
Copy Markdown
Contributor

Bumps postcss from 8.5.15 to 8.5.33.

Release notes

Sourced from postcss's releases.

8.5.33

  • Fixed unquoted url() with /* after a comma (by @​MFA-G).
  • Fixed url (…) with a space before the bracket being parsed as URL.
  • Fixed unquoted uppercase URL() parsing (by @​Don-Yin).
  • Fixed empty source in CssSyntaxError on long lines (by @​simpleqt).
  • Fixed line breaks on source map annotation removal (by @​wozhenbang2004).
  • Fixed Declaration#important types (by @​johnhldiver-beep).

8.5.32

  • Fixed Input#origin() without opts.from (by @​wleeaf).
  • Fixed final-word lookup without source offsets (by @​Don-Yin).
  • Fixed explicit start in Warning#toString() (by @​Don-Yin).
  • Fixed Promise semantics in LazyResult#finally() (by @​Don-Yin).

8.5.31

8.5.30

  • Fix broken map on </style> escaping (by @​Rufflet).

8.5.29

8.5.28

  • Fixes types regression.

8.5.27

8.5.26

  • Fixed list.split() regression (by @​lazerg).
  • Track symlinks in path protection in source map loading (by @​drengir1).

8.5.25

  • Fixed 8.5.17 visitor regression.
  • Fixed list.split() for non-string values (by @​amir-rezaei).

8.5.24

  • Preserve the BOM after the processing (by @​hdimer).

8.5.23

  • Do not load source map without opts.from for security reasons.

... (truncated)

Changelog

Sourced from postcss's changelog.

8.5.33

  • Fixed unquoted url() with /* after a comma (by @​MFA-G).
  • Fixed url (…) with a space before the bracket being parsed as URL.
  • Fixed unquoted uppercase URL() parsing (by @​Don-Yin).
  • Fixed empty source in CssSyntaxError on long lines (by @​simpleqt).
  • Fixed line breaks on source map annotation removal (by @​wozhenbang2004).
  • Fixed Declaration#important types (by @​johnhldiver-beep).

8.5.32

  • Fixed Input#origin() without opts.from (by @​wleeaf).
  • Fixed final-word lookup without source offsets (by @​Don-Yin).
  • Fixed explicit start in Warning#toString() (by @​Don-Yin).
  • Fixed Promise semantics in LazyResult#finally() (by @​Don-Yin).

8.5.31

8.5.30

  • Fix broken map on </style> escaping (by @​Rufflet).

8.5.29

8.5.28

  • Fixes types regression.

8.5.27

8.5.26

  • Fixed list.split() regression (by @​lazerg).
  • Track symlinks in path protection in source map loading (by @​drengir1).

8.5.25

... (truncated)

Commits
  • b6316e5 Release 8.5.33 version
  • 0ffa3ee Update dependencies
  • 46ab74a More proper fix
  • ba705bc fix: tokenize an unquoted url() after a comma (#2195)
  • 93452db docs: fix typo in plugin guidelines heading (#2196)
  • 812d362 docs: remove unsupported postcss-sanitize plugin (#2192)
  • 4740f8a Fix CRLF line break cleanup before source map annotations (#2187)
  • 2ab84dd fix: tokenize uppercase url() as a url (#2185)
  • 17e54b7 fix: show source around long lines for errors without range (#2184)
  • 2faedf9 fix: include undefined in Declaration.important getter type (#2181)
  • Additional commits viewable in compare view
Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for postcss since your current version.


@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Aug 1, 2026
@ems-pr-review

ems-pr-review Bot commented Aug 1, 2026

Copy link
Copy Markdown

It looks like you are reviewing a Dependabot upgrade PR! 🛠️
That’s great! Keeping our packages up to date to fix security issues in our stack is super important. Team Application Security wants to help make this process as easy and low friction as possible while still moving at pace.

We aim to merge Dependabot PRs within the below timeframes. The objectives are based on the severity of the security vulnerability we are mitigating with the upgrade:

Severity Target Merge (days)
CRITICAL 7 days
HIGH 14 days
MEDIUM 30 days
LOW 90 days

🎯 Target merge date for this PR: 15/08/2026 🎯

FAQ

What if we aren’t vulnerable to this particular CVE? Do we still have to upgrade the package? It’s still a good idea to upgrade the package if we can. With new code patterns and paths being introduced every day, we have no guarantee that we won’t later make ourselves vulnerable. Keeping packages up to date as a matter of due course is also good hygiene.
What if we’re not vulnerable and upgrading is going to be a lot of work? In these cases it’s a good idea to list out the steps you took to confirm we are not vulnerable in this PR. The PR can then be closed and the corresponding Dependabot Alert should be dismissed with the triage steps included as a comment. Please get in touch with Team Application Security via #ask-security before dismissing any CRITICAL alerts.
This is a major version upgrade that requires substantial code refactoring. What should I do? If the upgrade requires substantial refactoring then it is possible that we will miss the objectives we have outlined above. In these cases, you should add the dependabot-refactor-required label to this PR and ping #ask-security for further advice.

@socket-security

socket-security Bot commented Aug 1, 2026 •

Copy link
Copy Markdown

Caution

Review the following alerts detected in dependencies.

According to your organization's Security Policy, you must resolve all "Block" alerts before proceeding. Learn more about Socket for GitHub.

Priority Alert  (click "▶" to expand/collapse) Action
Low priority
Recently published: npm @rollup/rollup-android-arm-eabi published 2 days ago

Location: Package overview

From: package.json → npm/vitest@4.1.0 → npm/@rollup/rollup-android-arm-eabi@4.68.3

ℹ Read more on: This package | This alert | What are recently published artifacts?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should either be allowlisted to allow recently-published versions, or an older version should be used instead.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@rollup/rollup-android-arm-eabi@4.68.3. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Block
Low priority
Recently published: npm @rollup/rollup-android-arm64 published 2 days ago

Location: Package overview

From: package.json → npm/vitest@4.1.0 → npm/@rollup/rollup-android-arm64@4.68.3

ℹ Read more on: This package | This alert | What are recently published artifacts?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should either be allowlisted to allow recently-published versions, or an older version should be used instead.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@rollup/rollup-android-arm64@4.68.3. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Block
Low priority
Recently published: npm @rollup/rollup-android-x64 published 2 days ago

Location: Package overview

From: package.json → npm/vitest@4.1.0 → npm/@rollup/rollup-android-x64@4.68.3

ℹ Read more on: This package | This alert | What are recently published artifacts?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should either be allowlisted to allow recently-published versions, or an older version should be used instead.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@rollup/rollup-android-x64@4.68.3. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Block
Low priority
Recently published: npm @rollup/rollup-darwin-arm64 published 2 days ago

Location: Package overview

From: package.json → npm/vitest@4.1.0 → npm/@rollup/rollup-darwin-arm64@4.68.3

ℹ Read more on: This package | This alert | What are recently published artifacts?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should either be allowlisted to allow recently-published versions, or an older version should be used instead.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@rollup/rollup-darwin-arm64@4.68.3. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Block
Low priority
Recently published: npm @rollup/rollup-darwin-x64 published 2 days ago

Location: Package overview

From: package.json → npm/vitest@4.1.0 → npm/@rollup/rollup-darwin-x64@4.68.3

ℹ Read more on: This package | This alert | What are recently published artifacts?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should either be allowlisted to allow recently-published versions, or an older version should be used instead.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@rollup/rollup-darwin-x64@4.68.3. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Block
Low priority
Recently published: npm @rollup/rollup-freebsd-arm64 published 2 days ago

Location: Package overview

From: package.json → npm/vitest@4.1.0 → npm/@rollup/rollup-freebsd-arm64@4.68.3

ℹ Read more on: This package | This alert | What are recently published artifacts?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should either be allowlisted to allow recently-published versions, or an older version should be used instead.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@rollup/rollup-freebsd-arm64@4.68.3. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Block
Low priority
Recently published: npm @rollup/rollup-freebsd-x64 published 2 days ago

Location: Package overview

From: package.json → npm/vitest@4.1.0 → npm/@rollup/rollup-freebsd-x64@4.68.3

ℹ Read more on: This package | This alert | What are recently published artifacts?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should either be allowlisted to allow recently-published versions, or an older version should be used instead.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@rollup/rollup-freebsd-x64@4.68.3. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Block
Low priority
Recently published: npm @rollup/rollup-linux-arm-gnueabihf published 2 days ago

Location: Package overview

From: package.json → npm/vitest@4.1.0 → npm/@rollup/rollup-linux-arm-gnueabihf@4.68.3

ℹ Read more on: This package | This alert | What are recently published artifacts?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should either be allowlisted to allow recently-published versions, or an older version should be used instead.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@rollup/rollup-linux-arm-gnueabihf@4.68.3. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Block
Low priority
Recently published: npm @rollup/rollup-linux-arm-musleabihf published 2 days ago

Location: Package overview

From: package.json → npm/vitest@4.1.0 → npm/@rollup/rollup-linux-arm-musleabihf@4.68.3

ℹ Read more on: This package | This alert | What are recently published artifacts?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should either be allowlisted to allow recently-published versions, or an older version should be used instead.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@rollup/rollup-linux-arm-musleabihf@4.68.3. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Block
Low priority
Recently published: npm @rollup/rollup-linux-arm64-gnu published 2 days ago

Location: Package overview

From: package.json → npm/vitest@4.1.0 → npm/@rollup/rollup-linux-arm64-gnu@4.68.3

ℹ Read more on: This package | This alert | What are recently published artifacts?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should either be allowlisted to allow recently-published versions, or an older version should be used instead.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@rollup/rollup-linux-arm64-gnu@4.68.3. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Block
Low priority
Recently published: npm @rollup/rollup-linux-arm64-musl published 2 days ago

Location: Package overview

From: package.json → npm/vitest@4.1.0 → npm/@rollup/rollup-linux-arm64-musl@4.68.3

ℹ Read more on: This package | This alert | What are recently published artifacts?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should either be allowlisted to allow recently-published versions, or an older version should be used instead.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@rollup/rollup-linux-arm64-musl@4.68.3. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Block
Low priority
Recently published: npm @rollup/rollup-linux-loong64-gnu published 2 days ago

Location: Package overview

From: package.json → npm/vitest@4.1.0 → npm/@rollup/rollup-linux-loong64-gnu@4.68.3

ℹ Read more on: This package | This alert | What are recently published artifacts?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should either be allowlisted to allow recently-published versions, or an older version should be used instead.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@rollup/rollup-linux-loong64-gnu@4.68.3. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Block
Low priority
Recently published: npm @rollup/rollup-linux-loong64-musl published 2 days ago

Location: Package overview

From: package.json → npm/vitest@4.1.0 → npm/@rollup/rollup-linux-loong64-musl@4.68.3

ℹ Read more on: This package | This alert | What are recently published artifacts?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should either be allowlisted to allow recently-published versions, or an older version should be used instead.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@rollup/rollup-linux-loong64-musl@4.68.3. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Block
Low priority
Recently published: npm @rollup/rollup-linux-ppc64-gnu published 2 days ago

Location: Package overview

From: package.json → npm/vitest@4.1.0 → npm/@rollup/rollup-linux-ppc64-gnu@4.68.3

ℹ Read more on: This package | This alert | What are recently published artifacts?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should either be allowlisted to allow recently-published versions, or an older version should be used instead.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@rollup/rollup-linux-ppc64-gnu@4.68.3. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Block
Low priority
Recently published: npm @rollup/rollup-linux-ppc64-musl published 2 days ago

Location: Package overview

From: package.json → npm/vitest@4.1.0 → npm/@rollup/rollup-linux-ppc64-musl@4.68.3

ℹ Read more on: This package | This alert | What are recently published artifacts?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should either be allowlisted to allow recently-published versions, or an older version should be used instead.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@rollup/rollup-linux-ppc64-musl@4.68.3. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Block
Low priority
Recently published: npm @rollup/rollup-linux-riscv64-gnu published 2 days ago

Location: Package overview

From: package.json → npm/vitest@4.1.0 → npm/@rollup/rollup-linux-riscv64-gnu@4.68.3

ℹ Read more on: This package | This alert | What are recently published artifacts?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should either be allowlisted to allow recently-published versions, or an older version should be used instead.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@rollup/rollup-linux-riscv64-gnu@4.68.3. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Block
Low priority
Recently published: npm @rollup/rollup-linux-riscv64-musl published 2 days ago

Location: Package overview

From: package.json → npm/vitest@4.1.0 → npm/@rollup/rollup-linux-riscv64-musl@4.68.3

ℹ Read more on: This package | This alert | What are recently published artifacts?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should either be allowlisted to allow recently-published versions, or an older version should be used instead.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@rollup/rollup-linux-riscv64-musl@4.68.3. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Block
Low priority
Recently published: npm @rollup/rollup-linux-s390x-gnu published 2 days ago

Location: Package overview

From: package.json → npm/vitest@4.1.0 → npm/@rollup/rollup-linux-s390x-gnu@4.68.3

ℹ Read more on: This package | This alert | What are recently published artifacts?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should either be allowlisted to allow recently-published versions, or an older version should be used instead.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@rollup/rollup-linux-s390x-gnu@4.68.3. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Block
Low priority
Recently published: npm @rollup/rollup-linux-x64-gnu published 2 days ago

Location: Package overview

From: package.json → npm/vitest@4.1.0 → npm/@rollup/rollup-linux-x64-gnu@4.68.3

ℹ Read more on: This package | This alert | What are recently published artifacts?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should either be allowlisted to allow recently-published versions, or an older version should be used instead.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@rollup/rollup-linux-x64-gnu@4.68.3. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Block
Low priority
Recently published: npm @rollup/rollup-linux-x64-musl published 2 days ago

Location: Package overview

From: package.json → npm/vitest@4.1.0 → npm/@rollup/rollup-linux-x64-musl@4.68.3

ℹ Read more on: This package | This alert | What are recently published artifacts?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should either be allowlisted to allow recently-published versions, or an older version should be used instead.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@rollup/rollup-linux-x64-musl@4.68.3. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Block
Low priority
Recently published: npm @rollup/rollup-openbsd-x64 published 2 days ago

Location: Package overview

From: package.json → npm/vitest@4.1.0 → npm/@rollup/rollup-openbsd-x64@4.68.3

ℹ Read more on: This package | This alert | What are recently published artifacts?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should either be allowlisted to allow recently-published versions, or an older version should be used instead.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@rollup/rollup-openbsd-x64@4.68.3. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Block
Low priority
Recently published: npm @rollup/rollup-openharmony-arm64 published 2 days ago

Location: Package overview

From: package.json → npm/vitest@4.1.0 → npm/@rollup/rollup-openharmony-arm64@4.68.3

ℹ Read more on: This package | This alert | What are recently published artifacts?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should either be allowlisted to allow recently-published versions, or an older version should be used instead.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@rollup/rollup-openharmony-arm64@4.68.3. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Block
Low priority
Recently published: npm @rollup/rollup-win32-arm64-msvc published 2 days ago

Location: Package overview

From: package.json → npm/vitest@4.1.0 → npm/@rollup/rollup-win32-arm64-msvc@4.68.3

ℹ Read more on: This package | This alert | What are recently published artifacts?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should either be allowlisted to allow recently-published versions, or an older version should be used instead.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@rollup/rollup-win32-arm64-msvc@4.68.3. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Block
Low priority
Recently published: npm @rollup/rollup-win32-ia32-msvc published 2 days ago

Location: Package overview

From: package.json → npm/vitest@4.1.0 → npm/@rollup/rollup-win32-ia32-msvc@4.68.3

ℹ Read more on: This package | This alert | What are recently published artifacts?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should either be allowlisted to allow recently-published versions, or an older version should be used instead.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@rollup/rollup-win32-ia32-msvc@4.68.3. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Block
See 4 more rows in the dashboard

View full report

@bscanlan

Copy link
Copy Markdown
Member

@dependabot recreate

@dependabot dependabot Bot changed the title Bump postcss from 8.5.15 to 8.5.25 Bump postcss from 8.5.15 to 8.5.26 Aug 27, 2026
@dependabot
dependabot Bot force-pushed the dependabot/npm_and_yarn/postcss-8.5.25 branch from b07be26 to df4ac0e Compare August 27, 2026 10:19
bscanlan
bscanlan previously approved these changes Aug 27, 2026

@bscanlan bscanlan left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Dependency bump — approving as part of the Dependabot backlog sweep.

@bscanlan
bscanlan enabled auto-merge (squash) August 27, 2026 11:53
@bscanlan

Copy link
Copy Markdown
Member

@dependabot rebase

~ Automated via Claude

Bumps [postcss](https://github.com/postcss/postcss) from 8.5.15 to 8.5.33.
- [Release notes](https://github.com/postcss/postcss/releases)
- [Changelog](https://github.com/postcss/postcss/blob/main/CHANGELOG.md)
- [Commits](postcss/postcss@8.5.15...8.5.33)

---
updated-dependencies:
- dependency-name: postcss
  dependency-version: 8.5.25
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot changed the title Bump postcss from 8.5.15 to 8.5.26 Bump postcss from 8.5.15 to 8.5.33 Nov 15, 2026
@dependabot
dependabot Bot force-pushed the dependabot/npm_and_yarn/postcss-8.5.25 branch from df4ac0e to 863f295 Compare November 15, 2026 16:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant