chore: bump postcss to 8.5.10#93288
Merged
eps1lon merged 3 commits intovercel:canaryfrom Apr 29, 2026
Merged
Conversation
Contributor
Tests PassedCommit: b394dd2 |
Member
|
In case people find the PR but not the issue:
|
Fixes the moderate-severity advisory GHSA-qx2v-qp2m-jg93 by upgrading postcss from 8.4.31 to 8.5.10 in both the Next.js package and the workspace devDependencies. pnpm-lock.yaml regenerated accordingly.
postcss 8.5 enriched the "Unknown word" error message with the offending token, breaking the inline snapshots in ReactRefreshLogBox tests on the webpack flavor.
4f2b7ef to
b394dd2
Compare
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fixes the moderate-severity advisory GHSA-qx2v-qp2m-jg93 by upgrading postcss from 8.4.31 to 8.5.10 in both the Next.js package and the workspace devDependencies. pnpm-lock.yaml regenerated accordingly.
Note that this vulnerability does not affect Next.js users unless they build from untrusted source code (which would have more severe security implications). We're merging this to reduce noise from security scanners.
Fixes #93234