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
docs(compatibility): point HTTPS_PROXY work to GitHub, not v1.10.4
v1.10.4 doesn't exist as a public version label — referring to it on the
marketing page set expectations. Replace all 'v1.10.4' mentions with
'tracked on GitHub', and link the legend's badge text to the issues page.
Mode badges and per-platform notes stay the same otherwise.
{ model: 'HTTP CONNECT proxy', examples: 'corp networks with explicit proxy URL', today: '~ WSS dial honors HTTPS_PROXY; registry TLS dial does not', needed: 'v1.10.4: registry through HTTPS_PROXY' },
107
+
{ model: 'HTTP CONNECT proxy', examples: 'corp networks with explicit proxy URL', today: '~ WSS dial honors HTTPS_PROXY; registry TLS dial does not', needed: 'tracked on GitHub — registry over HTTPS_PROXY' },
108
108
{ model: 'Transparent TLS interception', examples: 'Zscaler, Fortinet, Palo Alto, BlueCoat, Netskope', today: '✓ Works with -tls-trust=system (corp CA in OS store — v1.10.3 default)', needed: 'already supported' },
109
-
{ model: 'HTTP-proxy-only sandbox', examples: 'Replit Agent, Devin, Docker AI Sandbox', today: '✗ Blocked — daemon needs raw TCP to :443', needed: 'v1.10.4: full HTTPS_PROXY via CONNECT' },
109
+
{ model: 'HTTP-proxy-only sandbox', examples: 'Replit Agent, Devin, Docker AI Sandbox', today: '✗ Blocked — daemon needs raw TCP to :443', needed: 'tracked on GitHub — HTTPS_PROXY via CONNECT' },
0 commit comments