chore(deps): move pnpm overrides to pnpm-workspace.yaml#3371
Merged
Conversation
pnpm 11.2.0 stopped reading the `pnpm` field from package.json, silently disabling all eight security-floor overrides. The warning surfaced during the daily autoheal validation: [WARN] The "pnpm" field in package.json is no longer read by pnpm. The following keys were ignored: "pnpm.overrides". The stale lockfile still resolved transitive packages above the floors, but a fresh install or Renovate resolver run could drift below them. This restores enforcement by moving the block into `pnpm-workspace.yaml` per current pnpm settings docs. Refs: https://pnpm.io/settings
marcusrbrown
approved these changes
May 24, 2026
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
2 participants
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.
Why
pnpm 11.2.0 silently dropped support for reading the
pnpmfield frompackage.json. Runningpnpm installnow emits:All eight security-floor overrides were being ignored on fresh installs:
ajv@8,brace-expansion,fast-uri,flatted,minimatch,picomatch,undici,yamlThe existing
pnpm-lock.yamlstill pinned transitive packages above the floors because it was generated when pnpm still read the field, but any resolver-driven update (Renovate, fresh checkout,--no-frozen-lockfile) could quietly drift below them.What
overridesblock frompackage.json→pnpm-workspace.yaml, which is where pnpm 11 looks per the current settings docs.pnpm-lock.yamlso theoverrides:block now lives at the top of the lockfile and pnpm enforces it on--frozen-lockfile.Verification
pnpm install— no warnings, lockfile honoredpnpm run lint— cleanpnpm run check-types— cleanpnpm test— 22 files / 644 passed (+3 todo)Risk
Minimal and reversible. The override semantics are unchanged; only the file location moved. Reverting is a single revert commit if anything regresses.