You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix(build): harden proxy forwarding and registry fetch fallback
Review fixes for the re-landed proxy work (#407, split from #404):
- docker build gets --add-host host.docker.internal:host-gateway
whenever proxy args are forwarded: the localhost rewrite was dead on
native Linux Engine (Docker Desktop/OrbStack resolve the name
implicitly, Engine does not). Verified against a real daemon.
- localhost rewrite now catches authenticated proxies: the old patterns
anchored on ://127.0.0.1 and missed http://user:pass@127.0.0.1:7890
(confirmed via make -n). Make macro and version-upgrade sed both
handle @127.0.0.1/@localhost.
- proxy userinfo never printed raw: log_proxy_config (build logs) and
version-upgrade's forwarding display redact user:pass@ to ***@.
Residual: make's own recipe echo still expands proxy values in a
local terminal; not worth silencing every build recipe over.
- npm registry fetch restores npm view's soft-fail contract: transient
curl failure returns empty and hits load_versions' warn-and-fallback
branch instead of aborting under set -euo pipefail (that branch was
dead code for npm tools).
- tests/version-upgrade.sh: fake curl now serves realistic dist-tags +
packument fixtures instead of empty strings (the stale npm view mocks
made the suite pass while no builds ran, then die on the missing
docker-build.log — the #404 CI red). npm mock is a tripwire: any npm
call fails loudly. New scenarios: proxied build asserts rewrite +
host-gateway + no credential leak; registry outage asserts warnings,
fallback to current, exit 0, no builds.
Close#407
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
0 commit comments