Conversation
Related: #73347 has the same root lockfile refresh; this PR additionally adds a root PostCSS override. The shared remediation is not redundant, but the two approaches should be consolidated by a maintainer. |
f097a63 to
ece9d7c
Compare
Rebase noteRebased onto current
|
|
Thanks for the focused dependency-security remediation. Current The existing member note identifies overlapping lockfile work in #73347; that consolidation is the remaining maintainer coordination point. No changes requested. This is an automated hermes-sweeper review. |
|
Closing as superseded. Current No objection to anyone picking up a fresher PostCSS bump from a current-main branch. |
What does this PR do?
Pins the root JavaScript workspace graph to PostCSS 8.5.24, the patched release, so transitive consumers cannot continue resolving the vulnerable 8.5.x range. The root lockfile is regenerated without unrelated package upgrades.
Related Issue
No linked issue.
Type of Change
Changes Made
overrides.postcsspin at 8.5.24.How to Test
npm ci --include=dev --ignore-scriptsnpm ls postcss --all— all consumers resolve to 8.5.24.npm audit --workspaces=falseandnpm audit --workspace ui-tui— zero findings.@hermes/ink, Desktop, web, and ui-tui.The web workspace currently reports a separate newly published React Router RSC advisory. Hermes uses Declarative Mode, not the affected Framework/RSC mode, and the only npm-suggested v7 resolution is a downgrade that would reintroduce the older advisory fixed by the intentional 7.17.0 bump. This PR does not mix that separate dependency decision into the PostCSS fix.
Validation
@hermes/inkbuild: passedgit diff --check: passedChecklist