Repository navigation
Conversation
|
Independent check at Installation succeeded only when both the forwarded user configuration and CA certificate were present. With neither configured or authentication only, TLS failed before HTTP. With the CA only, the registry received one unauthenticated request and returned In the successful case, lifecycle scripts remained disabled and neither configuration path appeared in the scanner environment. The checked-out runtime source and lockfile remained unchanged, and no external registry was contacted. This is loopback-only validation; it does not establish Socket Registry Firewall or general enterprise-registry compatibility. |
|
Thanks for independently validating this against an authenticated HTTPS registry. The TLS/auth matrix and confirmation that lifecycle scripts and scan-environment isolation remained intact are especially helpful. |
|
Merged the inventory test fixture from #2678 into I also checked registry selection with real npm and a synthetic lockfile whose tarball URL used |
Summary
Trusted Linux runners can now select their npm configuration and custom CA for the pinned CLI installation with
use-runner-npm-config: true. This supports registries that require runner-managed authentication or certificate trust. Fixes #2407.Changes
NPM_CONFIG_USERCONFIGandNODE_EXTRA_CA_CERTSwhen the input is enabled. Each supplied path must be absolute and resolve to a regular file.npm cisubprocess. The selected npm configuration may choose the registry. The installer uses the committed lockfile, disables lifecycle scripts, and has a private cache and global configuration.AI assistance: Codex was used to inspect the issue and repository, implement and test the change, review the final diff, and draft this pull request. The contributor reviewed the resulting code, public artifacts, and test results before submission.
Testing
On Linux x64 with Node 24,
npm run validatepassed typechecking, all 230 Action tests, metadata and documentation checks, and bundle reproducibility. The installer fixture exercised the default, user-config only, CA only, and combined settings. It checked the npm command, installer environment, scan environment, and cleanup.An independent contributor previously exercised real npm against an authenticated loopback HTTPS registry. The original contributor’s installed-CLI smoke test reached Bubblewrap and stopped when the VM kernel denied user namespace creation.
Risk and rollout
The input defaults to false. Opted-in workflows trust the selected npm and CA files during installation. A configuration that expands a token from the environment needs an alternative credential source because the installer does not inherit ambient npm tokens.
Public disclosure review