Conversation
The lockfile (which becomes `npm-shrinkwrap.json` in the published package) is out of sync. I just ran `npm i` with the expected npm version (10) and this is the result.
1bdaa89 to
1088b53
Compare
ndhoule
approved these changes
Nov 26, 2025
fabianrbz
added a commit
to Kong/developer.konghq.com
that referenced
this pull request
Dec 9, 2025
7 tasks
fabianrbz
added a commit
to Kong/developer.konghq.com
that referenced
this pull request
Dec 9, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
v23.10.0 introduced a bug where a user with
netlify-cliin theirpackage.jsondependencies (or dev deps) who rannpm ciencountered an error like this:Strictly speaking, we didn't introduce a bug, but we happened to introduce the necessary conditions to trigger an existing, latent
npmCLI bug.This PR fixes that bug and introduces multiple guardrails to prevent this type of issue in the future.
You can confirm with this prerelease:
netlify-cli@23.11.1-pre.fa6e4b9.Fixes #7769.
Details
290a34d fix(npm-shrinkwrap.json): update lockfile
The lockfile (which becomes
npm-shrinkwrap.jsonin the published package) is out of sync. I just rannpm iwith the expected npm version (10) and this is the result.Surprisingly, this is the root of the bug. The published shrinkwrap file was effectively corrupted, due to a bug in npm v11, and this happened because... ⤵
8a159be ci: downgrade to npm@10 when publishing and updating deps
In #7746 we updated GitHub Actions CI workflows to use node.js 24. Node.js 24 comes bundled with npm 11. This means the next release workflow after this PR started running npm commands with npm 11. This, as well as Renovate itself using npm 11 (inspect the lockfile diff closely) resulted in corrupting the lockfile.
To be more specific, I believe we're running into a variation on npm/cli#8767. But we've also struggled with other npm 11 lockfile bugs recently anyway: netlify/build#6640. We should avoid npm 11 altogether for now.
1088b53 test(e2e): verify
npm ciruns successfully in a project depending onnetlify-cliThis will prevent reintroducing the conditions to hit this npm cli bug.
Follow-ups
I had #7799 in this PR initially, but I pulled it out to get the fixes above out asap.
Co-authored-by: Nathan Houle nathan@nathanhoule.com