Skip to content

build: require npm 11.11 or newer - #80

Merged
oleksandr-nc merged 1 commit into
mainfrom
chore/npm-11-10
Oct 23, 2026
Merged

oleksandr-nc merged 1 commit into
mainfrom
chore/npm-11-10

Conversation

@oleksandr-nc

@oleksandr-nc oleksandr-nc commented Oct 23, 2026 •

Copy link
Copy Markdown
Contributor

Dependabot installs the npm version that engines.npm names, so with ^11.3.0 it updates the lock file with npm 11.3.0. Its vite security updates for jira and reddit ran npm update vite --package-lock-only on 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 the libc field 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.json only updates its copy of engines.

🤖 AI (if applicable)

  • The content of this PR was partly or fully generated using AI

Signed-off-by: Oleksander Piskun <oleksandr2088@icloud.com>
@oleksandr-nc oleksandr-nc changed the title build: require npm 11.10 or newer build: require npm 11.11 or newer Oct 23, 2026
@oleksandr-nc
oleksandr-nc merged commit e9e8544 into main Oct 23, 2026
27 checks passed
@oleksandr-nc
oleksandr-nc deleted the chore/npm-11-10 branch October 23, 2026 08:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant