fix(ci): pin npm to 11.12.1 via packageManager field#2416
Merged
LeighFinegold merged 1 commit intofinos:mainfrom May 5, 2026
Merged
fix(ci): pin npm to 11.12.1 via packageManager field#2416LeighFinegold merged 1 commit intofinos:mainfrom
LeighFinegold merged 1 commit intofinos:mainfrom
Conversation
Renovate's hosted runner uses npm 10 by default, which raises EOVERRIDE when re-resolving the workspace tree against the dompurify override (`^3.4.0`) and other caret-range overrides. The lockfile regen step then aborts and Renovate ships package.json updates with a stale package-lock.json, breaking every npm-based CI job on the resulting PR. npm 11.5+ handles the same overrides scenario without erroring. Adding `packageManager: npm@11.12.1` is the standard Corepack-honored signal to pick a specific npm; Renovate respects it, and it also pins local dev and any non-explicit CI step onto the same npm so all three stay aligned. Closes finos#2415. Sequenced after finos#2414 (CI Node 24 / npm 11).
Contributor
There was a problem hiding this comment.
Pull request overview
Pins the root npm version via the packageManager field so Renovate uses npm 11 when regenerating the workspace lockfile. In this monorepo, that targets the root npm workspace dependency flow intended to avoid stale package-lock.json updates on Renovate PRs.
Changes:
- Adds
packageManager: "npm@11.12.1"to the root workspacepackage.json. - Leaves the rest of the root npm workspace configuration unchanged.
- Attempts to centralize npm version selection for Renovate-driven lockfile regeneration.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
LeighFinegold
approved these changes
May 5, 2026
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.
Description
Adds
"packageManager": "npm@11.12.1"to the rootpackage.jsonso Renovate's hosted runner uses npm 11 when regenerating the workspace lockfile.Closes #2415.
Sequencing: depends on #2414 landing first (CI Node 24 / npm 11). Once #2414 merges this is purely additive — only the workspace
package.jsongains one field.Why
Renovate currently uses npm 10 by default and raises
EOVERRIDEwhen re-resolving the tree against thedompurify: ^3.4.0override (and will eventually do the same for any other caret-range entry inoverrides). The regen aborts; Renovate ships the unrelatedpackage.jsonupdates with a stalepackage-lock.json; CI fails onnpm ci. Most recent breakage: #2410.npm 11.5+ handles the same scenario without erroring — verified locally that
npm installagainst PR #2410's head with npm 11.12.1 produces a clean lockfile in ~15 seconds.packageManageris the Corepack-standard signal and is what Renovate's hosted runner reads to pick its npm version. CI is unaffected by this field — the workflows callnpmfromactions/setup-nodeand don't runcorepack enable, so they keep using whatever npm ships with the configured Node (npm 11 from Node 24 once #2414 lands). Local dev only sees the pinned npm if the contributor opts into Corepack. The alternative (renovate.jsonconstraints.npm) would also fix Renovate, butpackageManageris the more standard and tooling-friendly signal.Type of Change
Affected Components
cli/)calm/)calm-ai/)calm-hub/)calm-hub-ui/)calm-server/)calm-widgets/)docs/)shared/)calm-plugins/vscode/)Testing
Local verification:
npm installagainst PR #2410's head with npm 11.12.1 produces a clean lockfile diff and no EOVERRIDE. Once this PR merges, the next Renovate patch-update PR is the real test — itsnpm cistep should pass.Checklist