[BUG] error Couldn't find any versions for "libnpmversion" that matches "^3.0.7"

[San-Shui]

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

error Couldn't find any versions for "libnpmversion" that matches "^3.0.7"

Expected Behavior

No response

Steps To Reproduce

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

Environment

• npm:
• Node.js:
• OS Name:
• System Model Name:
• npm config:

; copy and paste output from `npm config ls` here

[dcroote]

We're seeing this cause Docker build failure in CI: https://github.com/api3dao/airnode/runs/8127741866?check_suite_focus=true#step:4:94

[seanjb]

Looks like this commit, bumped the version number for libnpmversion ^3.0.1 to ^3.0.7 44bfedc#diff-7ae45ad102eab3b6d7e7896acd08c427a9b25b346470d7bc6507b6481575d519
3.0.7 does not exist on the public NPM registry. This is causing a lot of downstream build failures for our projects.

[nadimdiazramzi]

Same here, massive impact, can we get an update please? All our pipelines are dead for the past 6 hrs.

[Esonhugh]

Also Get my CICD down

[zcoding]

+1

[AsidStorm]

Reproduced for us with semantic-release today.

Dockerfile for reproduce

FROM node:16.13.0 as build
CMD yarn global add semantic-release

Will try to downgrade semantic-release to 8.0.3 (which have lower npm version dependency) in few hours, if not be fixed.

[existe-deja]

If you use yarn, adding this to your package.json does the trick.

"resolutions": {
    "libnpmversion": "3.0.6"
}

[Esonhugh]

Change your Npm version at

"npm": "8.18.0"

also fix
and waiting for new the upgrade.

[joundy]

+1

[camfou]

+1