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
{{ message }}
Repository navigation
Unpin the e2e npm CLI (npm@11 → latest/12.x) once npm/cli#9722 ships fixed — revisit 2026-08-09 #440
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).
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).
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.
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
chore: date the npm pin's revisit (#440, 2026-08-09)
test: pin the e2e npm CLI install to an explicit major (#438) (#439)
chore(v0): bundle action
chore(release): bundle action
chore(v0): bundle action