Artifact deploys now retry when the server is rate limited or unavailable, and abort cancels retries.
What's wrong with this entry?
The /deploy/direct call now retries transient server responses instead of failing the deploy outright.
- 429 honours the retry-after header, capped at 30s.
- 503 retries with jittered exponential backoff up to a maximum attempt count.
- Each retry is logged, and a telemetry event records the attempt count and final status.
- A user abort cancels the retry loop.
deploy_503_retried
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.