Repository navigation
Conversation
Renovate's lockfile step fails with EALLOWREMOTE in every repository on Tailwind 4, so its pull requests carry a stale package-lock.json and fail npm ci. With --package-lock-only, npm 12 unpacks each package that declares bundleDependencies to read the bundle, and that fetch skips the registry-tarball exemption from the default allow-remote=none (npm/cli#9800). Tailwind's optional @tailwindcss/oxide-wasm32-wasi is such a package, served from registry.npmjs.org. Set allow-remote=all in the .npmrc Renovate writes for its own lockfile step. Repositories keep their own .npmrc, so npm ci in CI keeps npm 12's default refusal and still rejects a lockfile that resolves to a URL.
ecv
marked this pull request as ready for review
November 17, 2026 19:53
ecv
marked this pull request as draft
November 17, 2026 20:36
Contributor
Author
|
Closing in favour of per-repo npm constraints in the affected repos, which keep npm's remote-download guard on everywhere. See the security review findings. |
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
Security and dependency updates can't merge in any repository that uses Tailwind 4. Renovate fails to rebuild
package-lock.json, pushes the pull request with the old lockfile, and CI then failsnpm cibecausepackage.jsonandpackage-lock.jsonare out of sync. After this change, Renovate rebuilds those lockfiles and the pull requests below can pass CI once Renovate rebases them.Stuck pull requests:
@hono/node-server)Cause
Renovate runs npm 12, because none of these repositories pins an npm version. npm 12 defaults to
allow-remote=none. A normal registry install is exempt from that setting. But with--package-lock-only, npm unpacks every package that declaresbundleDependenciesso it can read what the bundle contains, and that fetch skips the exemption. Tailwind 4's optional@tailwindcss/oxide-wasm32-wasiis one of those packages, so npm refuses its own registry tarball:This is npm's bug, still open upstream: npm/cli#9800. The existing
replace-registry-host=alwayssetting fixed a different case, where the tarball's host doesn't match the registry. It doesn't help here, because the host already matches.Change
The preset adds
allow-remote=allto the.npmrcthat Renovate writes for its lockfile step.Warning
This relaxes one npm 12 safeguard, but only inside Renovate's lockfile step. That step runs with
--ignore-scripts. Each repository's own.npmrcand its CI keep npm 12's defaultallow-remote=none. So a lockfile that resolves a dependency to a URL still failsnpm ciin CI.allow-remote=rootis not enough, because the refused package is a transitive dependency. Remove the line once npm/cli#9800 is fixed.Not covered
app#236also fails onui/packaging/dmg/package-lock.jsonwithEBADPLATFORM(appdmgsupports only macOS, and Renovate runs on Linux). This preset can't fix that. It needs a change in that repository, for exampleos=darwininui/packaging/dmg/.npmrc.Test plan
npm install --package-lock-only --ignore-scripts --replace-registry-host=always @hono/node-server@2.1.6exits 1 with the EALLOWREMOTE error above--allow-remote=allsucceeds. The lockfile moves@hono/node-serverto 2.1.6, and everyresolvedURL stays onregistry.npmjs.orgnpm ci --ignore-scriptsunder npm 12.2.2 defaults (allow-remote=none) succeeds on the regenerated lockfilebin/validate-renovate-configpasses