Skip to content

fix(release): isolate distinct empty npm config files - #5

Merged
julien-atacama merged 1 commit into
mainfrom
julien@release-npm-config
Nov 16, 2026
Merged

julien-atacama merged 1 commit into
mainfrom
julien@release-npm-config

Conversation

@julien-atacama

Copy link
Copy Markdown

Fix the npm configuration probe used by future publication runs. npm rejects loading /dev/null simultaneously as user and global configuration; use a separate exclusively created empty private global config while preserving isolated runtime, credential and lifecycle policy. Add a real read-only npm --version regression for environment-only, flags-only and combined configuration. No npm package is published by this change; the immutable V1 0.1.0 tag and archive remain untouched.

@julien-atacama
julien-atacama merged commit 4225efd into main Nov 16, 2026
5 checks passed
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