What
When the Artifact tool publishes an artifact, it now works differently:
- If the publish has no slug yet (the short name in the artifact's web address), the tool first tries to reserve one before uploading.
- If the reservation fails, it writes a debug line ("could not reserve a slug before publishing") and publishes anyway, leaving the server to assign the slug. A 403 or 404 response on the reserve step is not reported as
reserve_unavailable; any other failure is. - A 404 response on a redeploy is no longer always reported as
multifile_unsupported; some of those 404s are now exempt. - A successful publish now records how many files were left out and which path it took: "preflight", "legacy" or "inline".
Before, a publish with no slug went straight to uploading.
Why
Publishes that start without a slug now try to get one before uploading, and still go through if that step fails. Fewer redeploy failures are reported as unsupported multi-file publishes.
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
Which "not found" errors on republishing are now handled differently is not stated.