If a deploy commit succeeds but the immediate /deploy/direct response comes back 503 after the slug is already known, the client now waits and retries against that known slug instead of failing the publish outright. The retry is logged via a new deploy_stranded_retried telemetry event.
Artifact publish retries once after a stranded 503 on deploy/direct
A publish whose deploy call returns 503 after the slug is known now waits and retries against that slug.
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
Bug FixesKind: in v2.1.257,
Bug FixesSection of the release