Group of 2 You'll notice
Publishing an artifact now shows specific messages when it's rate-limited, including retry timing and which step failed
What
The artifact publish tool now detects and reports rate-limit (HTTP 429) responses at each stage of publishing, preflight and upload alike, using a new response-checking helper. When a 429 is hit, a new message builder reports:
- that nothing was published and the request was rate-limited
- the reserved slug involved
- which step was refused (for example, staging a publish's copied files)
- retry-after-based wait-time information, so the user knows when to try again
A distinct 422 'contract is newer than preferred' handshake message was also added for a separate related failure mode.
Why
Previously a rate-limited or conflicting publish attempt likely surfaced as a generic failure. Now the error clearly explains that nothing was published, why, and when it's safe to retry, making it easier to recover from a failed artifact publish.