You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Every open npm dependency PR fails all eight CI jobs at npm ci, with the same error across three unrelated bumps (#337 vite, #338 @types/node, #339 typescript-eslint):
npm error `npm ci` can only install packages when your package.json and package-lock.json
npm error Missing: proxy-agent@8.0.2 from lock file
npm error Missing: agent-base@9.0.0 from lock file
... 13 packages, all in the nested puppeteer-core proxy-agent tree
main itself is green, and PR #336 passed 16/16 on the same base — so the lock on main is fine and the bumps are not individually at fault.
Cause
Three environments resolve this manifest with different npm majors, and nothing in the repo pins one:
Where
Runtime
npm
Nested entries under puppeteer-core
CI (ci.yaml, 7 jobs)
node 22.23.2
10.9.8
needs 26
Production (Dockerfile)
node 26-alpine
11.x
15
Dependabot
—
11.x
writes 15
Verified by regenerating main's manifest locally, both arms:
npm@10.9.8 install --package-lock-only → 26 nested entries, byte-identical to the committed lock
npm@11.19.1 install --package-lock-only → 15 nested entries, −216 lines; npm ci then succeeds under npm 11 (568 packages, rc=0)
So the committed lock is npm-10-shaped, Dependabot rewrites it npm-11-shaped, and CI's npm 10 rejects that as incomplete. Every future npm bump hits this.
Impact
All npm dependency updates are permanently blocked — auto-merge is armed on all three and cannot fire.
Separately, CI validates on node 22 while the image ships node 26, so the pipeline is not testing the runtime that reaches users.
Expected
CI, Dependabot and the production image agree on one Node/npm major, and dependency PRs merge on their own again.
Acceptance criteria
One Node major is used by ci.yaml, the Dockerfile, and engines.
package-lock.json is regenerated by that npm and npm ci succeeds in CI.
Activity
chore: agent-claim #340 nonce=3d760c8de0ae3843c779590e2d3ab17e
build: declare one Node toolchain and check every consumer reads it (#…