Under the hood
Publishing errors now record retry timing and reserved-slug details
What
When publishing an artifact fails, the error report sent for telemetry now includes a retryAfter value (taken from the server's retry-after response header), whether a reservedSlug (a name held for the artifact) exists, and a created field. When a rate-limit error occurs but a slug was already reserved, the extra explanatory text normally appended to the error message is now left out.
Why
This gives more precise information about why a publish attempt failed and whether it can be retried, and avoids cluttering the error message with redundant text when a slug reservation already succeeded.