You'll notice
Artifact publish now handles server rate-limit responses explicitly during upload and copy, showing a retry-after time
What
When publishing an artifact, the file-upload and cross-artifact-copy steps now specifically detect a rate-limited response from the server and call a dedicated handler for it, instead of treating it as a generic 'upload unavailable' error. The final error message shown for a failed deploy now includes a retryAfter value read from the server's response headers.
Why
This means that if artifact publishing is rate-limited by the server, you now get a clearer error that tells you when to retry, rather than a generic failure message.
One source agreesOne thing we can check says the same as this entry.
Anthropic's release notes agree
[VSCode] Added a Copy response button on responses and a typed /copy