Skip to content

Widen engines.pnpm to >=9.6.0 so Dependabot's pnpm 11 can run - #411

Merged
eberle1080 merged 1 commit into
mainfrom
fix/pnpm-engines-dependabot
Sep 15, 2026
Merged

eberle1080 merged 1 commit into
mainfrom
fix/pnpm-engines-dependabot

Conversation

@eberle1080

Copy link
Copy Markdown
Contributor

Summary

  • Change engines.pnpm from ^9.6.0 || ^10.8.0 to >=9.6.0 in package.json, and sync the mirrored root entry in package-lock.json.

Why

After #410 fixed the lockfile parse error, Dependabot got further and now fails on #389 with "Dependabot does not support your pnpm version".

Dependabot's image runs pnpm 11.17.0. pnpm always enforces the root project's engines.pnpm, so it refuses to install:

ERR_PNPM_UNSUPPORTED_ENGINE  Unsupported environment (bad pnpm and/or Node.js version)
Expected version: ^9.6.0 || ^10.8.0
Got: 11.17.0

Dependabot maps that exact message to its "unsupported pnpm version" error. It does try to activate a pnpm 10 via corepack to satisfy the range, but falls back to its bundled 11.x when that fails, so a packageManager pin would most likely hit the same fallback.

>=9.6.0 keeps the floor from #28 and drops the ceiling that only Dependabot trips on. An explicit || ^11.0.0 would break again when Dependabot moves to pnpm 12.

Verification

  • pnpm install --frozen-lockfile --lockfile-only passes with pnpm 10.28.0.
  • Same command passes with pnpm 11.17.0 (via npx pnpm@11.17.0), where it failed before.
  • pnpm 11 leaves pnpm-lock.yaml byte-identical, so no lockfile churn for anyone on pnpm 10.

Follow-up

After merge, comment @dependabot rebase on #389.

🤖 Generated with Claude Code

Dependabot's npm_and_yarn image now runs pnpm 11.17.0. pnpm always
enforces the root project's engines.pnpm field, so with the previous
range (^9.6.0 || ^10.8.0) it fails with ERR_PNPM_UNSUPPORTED_ENGINE and
Dependabot reports "does not support your pnpm version" on every rebase
attempt (see #389). Dependabot does try to activate a pnpm 10 via
corepack to satisfy the range, but falls back to its bundled 11.x when
that activation fails.

Drop the ceiling, keep the floor. Verified with pnpm 10.28.0 and
pnpm 11.17.0 using `pnpm install --frozen-lockfile --lockfile-only`;
pnpm 11 leaves pnpm-lock.yaml unchanged. The root entry in
package-lock.json is synced via `npm install --package-lock-only`.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
@eberle1080
eberle1080 merged commit 2f692f1 into main Sep 15, 2026
2 checks passed
@eberle1080
eberle1080 deleted the fix/pnpm-engines-dependabot branch September 15, 2026 20:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant