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
HomeReleasesv2.1.225entry #13

Claude Code v2.1.225 ·

Artifact publishes retry 429 and 503 with a live progress line

Artifact publishing now retries when the service is busy, showing a live attempt counter instead of failing.

You'll notice New Features
JSON All of v2.1.225
You'll noticeTier: how much it should matter to you
4Useful: my rating, 1 to 5
0Signal: worth watching, 1 to 5
ArtifactsArea: what it touches
New FeaturesKind: in v2.1.225,
What probably matters to youSection of the release
What

Publishing an artifact through /api/frame/deploy/direct now retries transient failures instead of failing outright, and shows the retry state while it happens.

Details
  • A 429 is retried once after the retry-after delay, capped; 503s are retried with backoff up to a maximum attempt count.
  • Retries honor the abort signal, logging "[artifact] /deploy/direct retry cancelled by user".
  • A new progress event type renders "Publish service temporarily unavailable" or "Publish service busy" followed by " — retrying (attempt N of M)…".
  • Telemetry deploy_503_retried / deploy_429_retried carries deploy_attempts and deploy_final_status.
  • onRetry and signal are threaded through the publish call chain. None of this existed in 2.1.224.
Evidence

artifact_publish_retry

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.225 →

Feedback