Skip to content

Unpin the e2e npm CLI (npm@11 → latest/12.x) once npm/cli#9722 ships fixed — revisit 2026-08-09 #440

Closed

Description

@thekevinbot

Follow-up to #438 / #439. The e2e fixture publish job pins npm install -g npm@11 because npm 12.0.0's published bundle is missing libnpmpublish's unscoped sigstore dependency, so every npm publish --provenance dies with MODULE_NOT_FOUND (upstream: npm/cli#9722, open and awaiting triage as of 2026-07-09).

Revisit on 2026-08-09 (one month out):

  1. Check [BUG] npm publish results in Cannot find module 'sigstore' npm/cli#9722 — fixed release shipped?
  2. Verify locally before touching CI: npm install -g npm@latest, then confirm require.resolve('sigstore', { paths: ['<global npm>/node_modules/libnpmpublish/lib'] }) resolves (this is the exact check that failed on 12.0.0).
  3. If fixed: bump the pin in .github/workflows/e2e-fixture-job.yml ("Pin npm to a Trusted-Publishing-capable version" step) to the fixed major and update its comment. The e2e fixture suite going green on the PR is the verification.
  4. If still broken: push this date out and note it here.

If the pin is still in place with no recorded decision after the revisit date, that's drift — the point of the date is that npm@11 doesn't quietly become load-bearing archaeology.

Activity

  1. added a commit that references this issue on Jul 16, 2026
    c278a45
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

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions