chore(deps): bump postcss and next in /web-ui

[dependabot]

Bumps postcss to 8.5.23 and updates ancestor dependency next. These dependencies need to be updated together.

Updates postcss from 8.4.31 to 8.5.23

Release notes

Sourced from postcss's releases.

8.5.23

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

8.5.22

• Fixed custom property losing semicolon before a comment (by @​sarathfrancis90).

8.5.21

• Fixed childless at-rule losing semicolon before comment (by @​sarathfrancis90).
• Fixed docs (by @​isker).

8.5.20

• Fixed missing space if AtRule#params is set after (by @​sarathfrancis90).
• Fixed mixing AST error on warnings (by @​MahinAnowar).

8.5.19

• Fixed cleaning before for new nodes inserted to Root (by @​MahinAnowar).

8.5.18

• Restricted loading previous source maps file to the opts.from folder for security reasons (use unsafeMap: true to disable the check).

8.5.17

• Fixed Maximum call stack size exceeded error.
• Fixed Prototype hijacking for postcss.fromJSON().
• Fixed Input#origin() for unmapped end position (by @​chatman-media).

8.5.16

• Fixed Input#origin() position (by @​mizdra).
• Fixed raws after rehydrating a JSON AST (by @​sarathfrancis90).
• Fixed putting parent-less node in nodes of new node (by @​MahinAnowar).
• Fixed computing offset in positionBy() (by @​greymoth-jp).
• Fixed rangeBy() on index: 0 (by @​sarathfrancis90).

8.5.15

• Fixed declaration parsing performance (by @​homanp).

8.5.14

• Fixed custom syntax regression (by @​43081j).

8.5.13

• Fixed postcss-scss commend regression.

8.5.12

• Fixed reading any file via user-generated CSS.
• Added opts.unsafeMap to disable checks.

8.5.11

• Fixed nested brackets parsing performance (by @​offset).

8.5.10

• Fixed XSS via unescaped </style> in non-bundler cases (by @​TharVid).

... (truncated)

Changelog

Sourced from postcss's changelog.

8.5.23

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

8.5.22

• Fixed custom property losing semicolon before a comment (by @​sarathfrancis90).

8.5.21

• Fixed childless at-rule losing semicolon before comment (by @​sarathfrancis90).
• Fixed docs (by @​isker).

8.5.20

• Fixed missing space if AtRule#params is set after (by @​sarathfrancis90).
• Fixed mixing AST error on warnings (by @​MahinAnowar).

8.5.19

• Fixed cleaning before for new nodes inserted to Root (by @​MahinAnowar).

8.5.18

• Restricted loading previous source maps file to the opts.from folder for security reasons (use unsafeMap: true to disable the check).

8.5.17

• Fixed Maximum call stack size exceeded error.
• Fixed Prototype hijacking for postcss.fromJSON().
• Fixed Input#origin() for unmapped end position (by @​chatman-media).

8.5.16

• Fixed Input#origin() position (by @​mizdra).
• Fixed raws after rehydrating a JSON AST (by @​sarathfrancis90).
• Fixed putting parent-less node in nodes of new node (by @​MahinAnowar).
• Fixed computing offset in positionBy() (by @​greymoth-jp).
• Fixed rangeBy() on index: 0 (by @​sarathfrancis90).

8.5.15

• Fixed declaration parsing performance (by @​homanp).

8.5.14

• Fixed custom syntax regression (by @​43081j).

8.5.13

... (truncated)

Commits

• eb9e1fe Release 8.5.23 version
• 9d19c78 Update dependencies
• 7beca13 Does no load source map file without opts.from
• decea51 Typo
• c18e30d Update EM banner
• 98a39ad Update EM banner
• a3e48c4 Release 8.5.22 version
• f49d691 Fix custom property losing its semicolon before a comment (#2117)
• 28e0daf Release 8.5.21 version
• 3d2b4e4 Update dependencies
• 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.

Updates next from 16.2.12 to 16.3.0

Release notes

Sourced from next's releases.

v16.3.0

Core Changes

• Update vendored lodash to 4.17.23 to fix CVE-2025-13465: #91558
• Fix invalid HTML response for route-level RSC requests in deployment adapter: #91541
• Normalize encoded dynamic placeholders in app routes: #91603
• Fix(pages-router): restore Content-Length and ETag for /_next/data/ JSON responses: #90304
• Update tokio from 1.43.0 to 1.47.3: #90945
• [turbopack] Simplify snapshotting logic: #91178
• Turbopack: enable server HMR for app route handlers: #91466
• turbo-tasks-backend: batch find_and_schedule_dirty using for_each_task_meta: #91497
• [turbopack] Use bail! instead of panic! for duplicate module ident error: #91636
• Skip loadBindings() Lightning CSS check during next start: #91538
• turbo-tasks-backend: batch schedule dirty tasks in aggregation_update: #91461
• Turbopack: Add importModule() support to webpack loaders: #89630
• turbo-persistence: fix mmap page alignment and improve error context in MetaFile::open_internal: #91640
• turbopack-css: demote recoverable CSS parse warnings to Warning severity: #91524
• feat(node-streams): add config flag, define-env, and env precedence test: #90427
• Rename /_next/webpack-hmr to /_next/hmr: #91415
• Add per-slot error attribution for instant validation using slot markers and config depth preference: #91610
• Handle encoded params further: #91627
• [turbopack] Respect {eval:true} in worker_threads constructors: #91666
• Fix missing route in otel spans without base-server: #91665
• [turbopack] Optimize compaction cpu usage: #91468
• Fix layout segment optimization: move app-page imports to server-utility transition: #91701
• Fix server actions in standalone mode with cacheComponents: #91711
• turbo-persistence: remove Unmergeable mmap advice: #91713
• turbopack: move "compact database" tracing span to backend layer: #91693
• Turbopack: lazy require metadata and handle TLA: #91705
• Fix adapter outputs for dynamic metadata routes: #91680
• Turbopack: fix webpack loader runner layer: #91727
• [turbopack] Remove incorrect debug_assert in try_read_task_cell: #91699
• Add module count field to module graph tracing spans: #91697
• turbopack-cli: add --persistent-caching flag for filesystem-backed cache: #91657
• Turbopack: pull in updated vercel/nft tests: #91651
• [turbopack] Improve regressed build speed on cross-compiled MUSL: #91477
• [Segment Bundling] [Scaffolding] Ensure inlining hint correctness: #91320
• [Segment Bundling] [Scaffolding] Track which segments can be omitted from prefetch: #91438
• Avoid deprecated TS node10 moduleResolution defaults: #91847
• [turbopack] Rebuild the docker build scripts: #91799
• Fix TS6 baseUrl deprecation for extended tsconfig: #91855
• Add next internal post-build CLI command for Turbopack database compaction: #91336
• Turbopack: Define Effect as a trait instead of a closure: #89080
• Turbopack: Implement TraceRawVcs and NonLocalValue correctly for Effects: #89133
• turbo-tasks-backend: improve print_cache_item_size instrumentation: #91742
• Turbopack: switch from base40 to base38 hash encoding (remove ~ and . from charset): #91832
• Use charCodeAt for normalizePathTrailingSlash: #91380
• Turbopack: Only patch lockfile when bindings fails to load: #91379
• [create-next-app] Skip interactive prompts when CLI flags are provided: #91840
• [devtools] Make instant navs panel draggable: #91914
• [Segment Bundling] Bundle static prefetches based on size: #91439

... (truncated)

Commits

• d73f562 v16.3.0
• 2e0d4cb Edits to turbopackFileSystemCache (#96531)
• 86df9c7 docs: cover direct visits and client navigations in the instant() e2e example...
• 47a52c0 [turbopack / next.js] Add an end-to-end test for new root detection (#96544)
• 8e878d4 Remove implicit Partial Prefetching opt-in from instant (#96539)
• e37ddd1 Fix deploy test TypeScript exclusions (#96545)
• 8a4920c docs: clarify first-party Skills workflows (#96495)
• 4344b83 Flag newly disabled deploy tests (#96505)
• 459617a fix: double fragment on navigation (#93132)
• cbf0cef Enable TypeScript CLI by default (#96497)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  You can disable automated security fix PRs for this repo from the Security Alerts page.

[frankbria]

Dependabot Triage — PR #1087: next 16.2.12 → 16.3.0 (with postcss, sharp)

Classification

• Update type: Security update (minor framework bump that carries transitive fixes)
• Security urgency: High
• Supply-chain risk: Medium (framework bump + sharp major; no tampering signals)

Key observations

• npm audit on the current lockfile confirms the exposure is real and is not the top-level postcss. Top-level postcss is already 8.5.23; the vulnerable copy is nested at node_modules/next/node_modules/postcss, pinned by next 16.2.12:
  • GHSA-r28c-9q8g-f849 (high) — path traversal in previous-source-map auto-loading
  • GHSA-6g55-p6wh-862q (high) — arbitrary file read via attacker-controlled sourceMappingURL
  • GHSA-qx2v-qp2m-jg93 (high) — XSS via unescaped </style> in stringify output
  • GHSA-fxqj-rqcc-2cmp (medium) — incomplete fix of the above
• Also lifts sharp 0.34.5 → 0.35.3, clearing GHSA-f88m-g3jw-g9cj (high, inherited libvips CVEs; vulnerable range sharp < 0.35.0).
• This is the only open PR that fixes any of these — the group bump in chore(deps): bump the npm-minor-patch group across 1 directory with 5 updates #1105 touches the already-patched top-level postcss and does not reach the nested copy.
• Two new lockfile packages: @img/sharp-freebsd-wasm32 and @img/sharp-webcontainers-wasm32. Both are official @img/* optional platform binaries expected for sharp 0.35.x, same namespace as the existing sharp platform packages. No lifecycle scripts added anywhere in the diff.
• Note for reviewers: the currently-red frontend checks are from a 2026-08-05 run against a since-moved base. The failures are TypeScript errors in test files (ProofRequirement.scope missing, jest mock typing) that have nothing to do with next — scope landed with the Phase 3.5C ScopeOut work. Re-running against current main is the honest test.

Recommendation

Merge now — gated on a fresh CI run after rebase

This is the highest-value frontend security PR open: three high postcss advisories plus a high sharp/libvips advisory, none of which any other PR fixes. The supply-chain signals are clean. The one thing not to do is merge on the stale red run, so it is being rebased first and will land once current-base CI is green.

Follow-up actions

• Rebased onto the fixed main; merging on fresh green rather than on the required-checks minimum, because the frontend build/test jobs are not in the required set and are exactly the ones that matter here.
• npm audit still reports @babel/core, brace-expansion, js-yaml and a low nanoid finding that no open PR addresses — tracked separately, see the sweep summary.

---

_{Supply-chain triage per the reviewing-dependabot-prs skill. Advisories verified via gh api /advisories/; action SHA pins verified by dereferencing the annotated tag to its commit. Green CI is a functional gate, not a supply-chain signal — a malicious lifecycle script passes CI happily, so the diff was scanned for one separately.}

[frankbria]

@dependabot rebase

[dependabot]

Looks like these dependencies are updatable in another way, so this is no longer needed.

[frankbria]

Correction to my triage above

My earlier comment claimed the red frontend checks here were stale artifacts of the 2026-08-05 base and that re-running against current main was the honest test. I ran that test, and I was wrong. The failures are real and caused by next 16.3.0.

Controlled locally on current main (9420cee4), same machine, same Node:

	npm run build
main as-is (npm ci)	exit 0, zero TypeScript errors
main + npm install next@^16.3.0	exit 1, 27 TypeScript errors

So the next 16.3.0 upgrade breaks the type-check. All 27 errors are in src/__tests__/** — zero in production source — spread over 12 files, dominated by TS2339 (9), TS2741 (5) and TS2322 (5). They look like the consequence of stricter/bundled typings coming with 16.3.0 (jest MockInstance, AppRouterInstance, SharedArrayBuffer vs ArrayBuffer), not a runtime regression.

What that means for the security picture, which is unchanged and still real: the upgrade does clear the outstanding advisories. Verified on the same lockfile —

• next 16.3.0 drops the nested node_modules/next/node_modules/postcss entirely (it falls back to the patched top-level 8.5.23), clearing GHSA-r28c-9q8g-f849, GHSA-6g55-p6wh-862q and GHSA-qx2v-qp2m-jg93 (all high)
• sharp 0.34.5 → 0.35.3 clears GHSA-f88m-g3jw-g9cj (high, libvips)
• npm audit: 7 vulnerabilities (6 high) → 4 (3 high)

So this is not a dependency bump that can be merged on CI alone — it needs the 27 test-type errors fixed alongside it. Tracked with the full inventory and a one-command reproduction in the follow-up issue.

Apologies for the premature call; the control run is what should have backed the original claim.