-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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.2Producing:
> [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?
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 [-w|--workspace ...]]
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
- In this environment...
- With this config...
- Run '...'
- See error...
Environment
No response