Repository navigation
fix: run Renovate lockfile updates on npm 11 - #238
Merged
Merged
Conversation
Renovate cannot regenerate the lockfiles here. With no npm pin in the repository it runs npm 12, which refuses to fetch the registry tarball of @tailwindcss/oxide-wasm32-wasi because that package declares bundleDependencies (npm/cli#9800). Every npm update, security fixes included, lands without a lockfile. Key changes: - Constrain Renovate's npm to <12 for this repository only. npm 11 regenerates ui/package-lock.json with every resolved URL on registry.npmjs.org, and npm's remote-download guard stays on. - Skip ui/packaging/dmg. appdmg is macOS-only and Renovate runs on Linux, so npm fails there with EBADPLATFORM on any version. npm's os setting does not lift that check, and force would turn off its other checks. ignorePaths replaces the preset list, so the defaults are restated. Drop the npm constraint once npm 12 ships the fix.
andrewb3000
approved these changes
Nov 17, 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.
Summary
Renovate cannot update npm dependencies in this repository: every lockfile update fails, so its pull requests (#236) carry a
package.jsonchange with no matchingpackage-lock.json. The same failure blocks the security fix datum-cloud/staff-portal#827 in staff-portal.With this change Renovate uses npm 11 here until npm 12 ships a fix for npm/cli#9800. npm's remote-download guard stays on: nothing relaxes
allow-remote, here or org-wide.Cause. No npm version is pinned here (no
engines.npm, nopackageManager, andlockfileVersion3 implies no limit), so Renovate runs the newest npm, 12.x. npm 12 refuses the registry tarball of@tailwindcss/oxide-wasm32-wasibecause that package declaresbundleDependencies:Change.
"constraints": {"npm": "<12"}inrenovate.json. Renovate checksconfig.constraints.npmbefore it derives a version frompackage.jsonor the lockfile (resolveToolConstraint, called fromnpm/post-update/npm.ts). The hosted Renovate app installs the npm version that satisfies the constraint.macOS packaging folder.
ui/packaging/dmg/package-lock.jsonfails on every npm version withEBADPLATFORM:appdmgdeclaresos: darwinand Renovate runs on Linux. The change addsui/packaging/dmg/**toignorePaths, so Renovate stops proposing updates forappdmg,patch-packageand theimage-sizeoverride there. The release workflow still installs them withnpm cion macOS. Two other options were rejected:.npmrcwithos=darwinin that folder does not work. On Linux, npm 11.21.2 readsosasdarwinand still fails theappdmgplatform check, because the setting only selects optional dependencies.force=truegets past the check, but it also turns off npm's other install checks, including in the macOS release job.ignorePathsreplaces the preset list instead of merging with it, so theconfig:recommendeddefaults are restated beside the new path.Expect npm 11 to add
inBundleentries under@tailwindcss/oxide-wasm32-wasi/node_modules/to the lockfile. These carry noresolvedURL, because their files ship inside the registry tarball.Removing the constraint is tracked in datum-cloud/staff-portal#848.
Test plan
Reproduced Renovate's command (
npm install --package-lock-only --no-audit --ignore-scripts, plus thename@versionarguments Renovate passes for lockfile-only updates) innode:24-bookworm, with Renovate'sreplace-registry-host=alwaysnpmrc:ui/with the lockfile-only update@tailwindcss/cli@4.3.5, npm 11.21.2: exits 0,oxide-wasm32-wasimoves to 4.3.5, 60 of 60resolvedURLs onhttps://registry.npmjs.org/EALLOWREMOTE, as in the PRui/packaging/dmgon Linux, npm 11.21.2:EBADPLATFORMwith no.npmrc, and again with.npmrcos=darwin; exits 0 only with--forcerenovate-config-validator --strict(Renovate 44) passes