{"version":"2.1.277","anchor":"artifact-publish-preserves-reservedslug-on-failure-except-f","canonical_anchor":"artifact-publish-preserves-reservedslug-on-failure-except-f","heading":"Artifact publish preserves reservedSlug on failure (except for PR-review pages)","tier":"notice","area":"Artifact Publish","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277\/e\/artifact-publish-preserves-reservedslug-on-failure-except-f","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277","markdown":"### Artifact publish preserves reservedSlug on failure (except for PR-review pages)\n\nFailed artifact publishes now keep their reserved slug so a retry can reuse it, except for PR-review pages\n\n**What**\n\nWhen publishing an artifact fails, Claude Code now carries the `reservedSlug` (the reserved address for the artifact) forward in the failure result, so that a retry can reuse the same slug instead of getting a new one. This applies unless the artifact's slug is stranded, conflicting, or gone, and unless the artifact is a `pr_review` page.\n\n**Why**\n\nThis avoids unnecessarily losing a reserved slug when a publish attempt fails, making retries more consistent, while excluding PR-review pages and problem-slug cases where reuse wouldn't make sense.\n\n- Area: Artifact Publish\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}