Repository navigation
[BC BREAK] version 11.6.2 breaks CI #8669
Description
Is there an existing issue for this?
- I have searched the existing issues
This issue exists in the latest npm version
- I am using the latest npm
Current Behavior
Hi,
We notice our CI starts failing for the following patch update:
| Package | Update | Change |
|---|---|---|
| npm | patch | 11.6.0 -> 11.6.2 |
Producing:
> [build 7/9] RUN --mount=type=cache,target=/root/.npm npm clean-install --legacy-peer-deps --logs-max=0:
2.769 npm error [--include <prod|dev|optional|peer> [--include <prod|dev|optional|peer> ...]]
2.769 npm error [--strict-peer-deps] [--foreground-scripts] [--ignore-scripts] [--no-audit]
2.769 npm error [--no-bin-links] [--no-fund] [--dry-run]
2.769 npm error [-w|--workspace <workspace-name> [-w|--workspace <workspace-name> ...]]
2.769 npm error [--workspaces] [--include-workspace-root] [--install-links]
2.769 npm error
2.769 npm error aliases: clean-install, ic, install-clean, isntall-clean
2.769 npm error
2.769 npm error Run "npm help ci" for more info
2.770 npm error Log files were not written due to the config logs-max=0
If i manually fiddle with it in a container, i see debug log:
`npm ci` can only install packages when your package.json and package-lock.json or npm-shrinkwrap.json are in sync. Please update your lock file with `npm install` before continuing.
But im not sure why our package.json and package-lock.json wouldnt be in sync ...
We always kept our package-lock.json in sync using npm clean-install --legacy-peer-deps && npm install --legacy-peer-deps --package-lock-only
Is there a related change in this patch release?
Expected Behavior
No response
Steps To Reproduce
No response
Environment
- npm: 11.6.2
- Node.js: 22.19
- OS Name: Ubunutu
- System Model Name: Gitub Actions
- npm config:
; "user" config from /root/.npmrc
engine-strict = true
; node bin location = /usr/local/bin/node
; node version = v22.19.0
; npm local prefix = /app
; npm version = 11.6.2
; cwd = /app
; HOME = /root
; Run `npm config ls -l` to show all defaults.
Activity
ro0NL commentedon Oct 13, 2025
i can confirm
11.6.1still works correctly:ebachle commentedon Oct 13, 2025
We're also seeing this, potentially specifically around optionalDependencies:
This is coming from entries in the package-lock.json that look something like this:
Our experience is also that rollback to
npm@11.6.1fixes this.Tezra commentedon Oct 14, 2025
This issue may be related to this issue. A possible work around is to run npm install twice in a row. (once to install/update, and once to fix minor lock discrepancies)
ro0NL commentedon Oct 14, 2025
@Tezra
im not really sure what the issue is at this point, or why we'd suddenly have "minor lock discrepancies"
DaSchTour commentedon Oct 15, 2025
I have experience the same with 11.6.1
My renovate MRs are broken since mid September and I blamed it on renovate not working properly.
romg974 commentedon Oct 15, 2025
Same issue with
npm ciand 11.6.2. Our solution was to revert to 11.6.1 until this is fixed. I have the feeling this is linked to #8593BarneyPowell commentedon Oct 16, 2025
FWIW We're seeing the same thing, in addition to other issues with 11.6.2, such as jest throwing an
Unable to find jest-utilerror which I fixed by rolling back to 11.6.1. Unsure if they are related - I'll try and create a repo to reproduce the issue.Our issue emerged due to an upstream docker image automatically installing latest npm, which we've now fixed @ 11.6.1.
[-][BUG] version 11.6.2 breaks CI[/-][+][BC BREAK] version 11.6.2 breaks CI[/+]ro0NL commentedon Oct 23, 2025
I'll assume this is on someone's radar at npm.
ebachle commentedon Oct 23, 2025
@ro0NL did this get fixed and that's why you're closing it? Or because it doesn't have responses? We're still pinned to an old version and I'd be happy to take over keeping track of this issue if it's still a problem.
ro0NL commentedon Oct 23, 2025
@ebachle it's not resolved; i assume this is issue is tracked by now, with someone at npm / a repo member
mstandley-tempus commentedon Oct 23, 2025
i wouldn't assume that -- can you reopen it and leave it open until we get confirmation that the npm team is on the case?
12 remaining items
v22 also ships buggy npm version
dominykas commentedon Nov 21, 2025
Still a problem in 11.6.3
TheRealWaldo commentedon Nov 25, 2025
@ro0NL please re-open this; there are many of us suffering from the problem and the only way for the maintainers to have this on their radar is if the issue is open.
None of us can re-open it for you.
ebachle commentedon Nov 25, 2025
@TheRealWaldo just shift over to #8726
It's a way better report and clearly OP isn't going to reopen
Fix npm ci failure: Upgrade npm to 11.6.4 to fix workspace bug
Fix npm ci failure: Upgrade npm to 11.6.4 to fix workspace bug
feat: enforce npm 11.6.4 via packageManager field
fix(ci): enforce npm version to prevent lockfile incompatibility
Fix lockfile issue by running npm install with version 11.8.0
ci: Update setup-node to v6 and node to v24 (current LTS)
Regenerate npm lockfile and remove npm upgrade workaround from CI
Regenerate npm lockfile and remove npm upgrade workaround from CI
Regenerate npm lockfile and remove npm upgrade workaround from CI (#13)
Switch from npm to pnpm for package management.
Switch from npm to pnpm for package management.