You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
ArtifactsArea: what it touches
ImprovementsKind: in v2.1.242,
ImprovementsSection of the release
What
An artifact content fetch blocked by a corporate egress proxy now reports its own reason code and an error naming the proxy's CONNECT status, rather than a generic relay failure, so a network policy problem is distinguishable from a service problem.
Details
A separate message explains that asset reads work only locally or from a cloud session with the gateway relay enabled.
Evidence
artifact content fetch refused by the environment's egress proxy
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
