Repository navigation
build: require npm 11.11 or newer - #80
Merged
Merged
Conversation
Signed-off-by: Oleksander Piskun <oleksandr2088@icloud.com>
oleksandr-nc
force-pushed
the
chore/npm-11-10
branch
from
October 23, 2026 07:55
dde4fb8 to
22799b1
Compare
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.
Dependabot installs the npm version that
engines.npmnames, so with^11.3.0it updates the lock file with npm 11.3.0. Its vite security updates for jira and reddit rannpm update vite --package-lock-onlyon 2026-10-22, and npm 11.3.0 to 11.5.2 abort that on both lock files with Cannot read properties of null (reading 'edgesOut'). npm 11.6 to 11.9 complete it but warn that they do not know--min-release-age, which Dependabot also passes and npm 11.10 added. Every npm before 11.11 also drops thelibcfield from the lock file's platform-specific packages, so Dependabot's lock file changes would remove it wherever it is set.CI already installs the newest npm 11 the range allows, and Node 24.14.1 and later ship npm 11.11 or newer.
package-lock.jsononly updates its copy ofengines.🤖 AI (if applicable)