{"version":"2.1.234","anchor":"failed-artifact-publish-tells-you-a-slug-was-already-reserve","canonical_anchor":"failed-artifact-publish-tells-you-a-slug-was-already-reserve","heading":"Failed artifact publish tells you a slug was already reserved","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234\/e\/failed-artifact-publish-tells-you-a-slug-was-already-reserve","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234","markdown":"### Failed artifact publish tells you a slug was already reserved\n\nA failed artifact publish now tells you a name was already reserved, so you retry against it.\n\n**What**\n\nIf a publish fails after reserving a name for the artifact, the result now tells you to retry against that reserved name rather than publishing fresh, instead of keeping the reserved value silently. Applies when the publish reserved a slug and none was supplied.\n\n**Evidence**\n\n`A slug WAS reserved`\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}