Skip to content

[BUG] <title>version 11.6.2 breaks CI #8718

Closed

Description

@vihvarn

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?

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

  1. In this environment...
  2. With this config...
  3. Run '...'
  4. See error...

Environment

No response

Activity

  1. added
    Bugthing that needs fixing
    Needs Triageneeds review for next steps
    on Nov 3, 2025
  2. alexsch01 commented on Nov 3, 2025

    @alexsch01
    Contributor

    This is word for word copied from #8669
    WTF

  3. v-kchindam-infy commented on Nov 3, 2025

    @v-kchindam-infy

    @vihvarn this issue looks like a copy of the previous one #8669. you have copied the issue as same . Closing this as duplicate

  4. ebachle commented on Nov 13, 2025

    @ebachle

    @kchindam-infy the other issue isn't resolved and the original author refuses to reopen it. That's why this probably got copy pasted.

    What's the best way to handle addressing the same issue in this case?

  5. pwnage101 commented on Nov 17, 2025

    @pwnage101

    @kchindam-infy I've been following this issue ever since we had to pin our .nvmrc to 24.11.0 (npm@11.6.1). I think we should make an effort to keep at least one of these issues open. #8669 (which this is a copy of) points to #8726 as the open issue to track the same bug, but I'm not actually convinced it's the same bug because the proposed workaround in the latter issue (run npm i twice) does not work. Only downgrading node and npm seems to work.

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

    Bugthing that needs fixingNeeds Triageneeds review for next steps

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions