Skip to content

feat!: default allow-git and allow-remote to none - #9466

Merged
owlstronaut merged 1 commit into
latestfrom
owlstronaut/allow-defaults
Jun 2, 2026
Merged

owlstronaut merged 1 commit into
latestfrom
owlstronaut/allow-defaults

Conversation

@owlstronaut

Copy link
Copy Markdown

BREAKING CHANGE: allow-git and allow-remote now default to "none"; set them to "all" (or "root") to install git or user-supplied tarball-URL dependencies.

@owlstronaut
owlstronaut requested review from a team as code owners June 2, 2026 16:25
@owlstronaut
owlstronaut force-pushed the owlstronaut/allow-defaults branch from 6093335 to 5a98ed1 Compare June 2, 2026 16:31
dhei
dhei previously approved these changes Jun 2, 2026
BREAKING CHANGE:  allow-git and allow-remote now default to "none"; set them to "all" (or "root") to install git or user-supplied tarball-URL dependencies.
@owlstronaut
owlstronaut merged commit caa3295 into latest Jun 2, 2026
59 checks passed
@owlstronaut
owlstronaut deleted the owlstronaut/allow-defaults branch June 2, 2026 20:12
Coldaine added a commit to MooseGooseConsulting/renovate-config that referenced this pull request Oct 23, 2026
Renovate installs the newest npm when a repository states none, now npm 12. npm 12 turned allow-remote off by default (npm/cli#9466), and --package-lock-only then refuses the registry tarball of packages with bundleDependencies, so package-lock.json updates failed with EALLOWREMOTE across the fleet (npm/cli#9800). Constrain npm to ^11 until a release with npm/cli#9818 ships.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.

2 participants