Skip to content

npm dependency PRs cannot merge: CI's npm 10 rejects the npm 11 lock Dependabot writes #340

Closed

Description

@devantler

🤖 Generated by the Agentic Engineer

Evidence

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

Rough size: small (CI matrix value + lock regeneration), but needs a full CI pass on the new runtime.

Activity

  1. added theissue type on Sep 20, 2026
  2. moved this to 🏃🏻‍♂️ In Progress in 🌊 Project Boardon Sep 20, 2026
  3. added a commit that references this issue on Sep 20, 2026
  4. moved this from 🏃🏻‍♂️ In Progress to 👀 In Review in 🌊 Project Boardon Sep 20, 2026
  5. moved this from 👀 In Review to ✅ Done in 🌊 Project Boardon Sep 20, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    Fields

    Priority

    None yet

    Effort

    None yet

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions