Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.234 ·

Publishing tells relay failures apart from real service answers

A publish answer that didn't come from the artifact service is reported as a relay error with its status.

You'll notice Improvements
JSON All of v2.1.234
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.234,
ImprovementsSection of the release
What

When a publish, deploy or upload answer did not actually come from the artifact service, it is now reported as a relay error carrying the HTTP status and a message saying the publish was not completed, instead of being parsed as if it were a deploy result.

Details
  • Responses carry a marker recording whether they came from the artifact service itself.
  • New telemetry reasons: relay_error, upload_relay_error, prepare_upload_relay_error.
  • The related HTTP call sites dropped their per-call host, auth and status-validation options.
Evidence

prepare_upload_relay_error

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

See this entry in the whole of v2.1.234 →

Feedback