You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
0Signal: worth watching, 1 to 5
ArtifactsArea: what it touches
New FeaturesKind: in v2.1.225,
New FeaturesSection of the release
What
Publish and deploy calls go through a shared retry wrapper that retries HTTP 503 using a delay derived from retry-after, and the transcript shows why it is waiting instead of appearing to hang.
Details
Retry progress is reported as an artifact_publish_retry event, rendered by a new UI component.
The line reads "Publish service temporarily unavailable" for a 503 and "Publish service busy" otherwise, followed by an attempt counter.
Telemetry records "deploy_503_retried" and "deploy_429_retried" with a deploy_attempts field.
Evidence
Publish service temporarily unavailable
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
