Files
fission-ai__openspec/website/pnpm-workspace.yaml
Clay Good e4e112d94f chore(deps): declare pnpm overrides only in pnpm-workspace.yaml (#1816)
The security overrides were declared twice: in pnpm-workspace.yaml, with
the advisory comments explaining each pin, and again under
package.json's pnpm.overrides. The copies are not additive — pnpm 10
uses package.json's block instead of the workspace list when both are
present — and Dependabot rewrites plain-name entries in package.json
whenever it bumps the same package. So a routine bump silently
displaces the pins that patch advisories, and fails the equality test
that guards them (#1812).

Keeps one declaration, in the file that carries the reasoning, and
asserts the mirror stays gone.

Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
2026-09-09 17:47:22 +00:00

21 lines
866 B
YAML

packages:
- '.'
allowBuilds:
esbuild@0.28.2: true
# The only declaration of these. A `pnpm.overrides` block in package.json does not
# merge with this list — pnpm 10 uses it *instead of* this file (verified: a lone
# entry there produced a lockfile with only that override). Dependabot rewrites
# plain-name entries in package.json when it bumps the same package, so a mirrored
# copy there both drifts and silently takes precedence over these advisory pins.
overrides:
postcss: ^8.5.28
sharp: ^0.35.3
brace-expansion@<=5.0.8: '>=5.0.9 <6'
fast-uri@<3.1.6: ^3.1.6
# GHSA-2v37-7h3g-55p8 / CVE-2026-67213 — nanoid infinite loop on size=0. Build-time
# only (transitive via postcss); this is a statically exported site with no server
# runtime. Remove once transitive nanoid is >=3.3.17 (check: pnpm why nanoid).
nanoid@<3.3.17: '>=3.3.17 <4'