You'll notice
Useful3 Signal2
Artifact publish failures now explain refusals and tell you the reserved slug so you can retry.
What's wrong with this entry?
Anonymous. No account, no email.
What
Publishing an artifact now explains a 422 refusal directly instead of the old "server kept reporting missing content" loop message, a cancelled publish tells you the slug it reserved so you can retry to it, and an auto-published edit that was not approved now says so and points at the artifact owner.
Details
- The 422 message states the deploy was refused and that the re-check before re-sending also failed.
- A new telemetry event
prepare_rerun_failedcarriesprepare_statusfor that case. - The declined auto-publish is a distinct outcome,
auto_mode_declined, whose text says the edit was not approved for automatic publishing and that the artifact owner can make the change from their own session.
Evidence
prepare_rerun_failed
Strings lifted out of the shipped bundle, so the claim above can be checked against them.