{"version":"2.1.282","anchor":"artifacts-publish-reuses-a-reserved-slug-and-runs-the-prefl","canonical_anchor":"artifacts-publish-reuses-a-reserved-slug-and-runs-the-prefl","heading":"Artifact publishing reuses a reserved address and pre-checks large updates","tier":"notice","area":"Artifacts","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282\/e\/artifacts-publish-reuses-a-reserved-slug-and-runs-the-prefl","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282","markdown":"### Artifact publishing reuses a reserved address and pre-checks large updates\n\nPublishing an artifact without an address now reuses one already reserved for it, and large updates get a pre-check before upload\n\n**Unclear.** The size limit and where the reserved slug comes from are not known.\n\n**What**\n\nA slug is the short name in a published artifact's web address. Two things changed when you publish:\n\n- If no slug is given, Claude Code now starts from one already reserved for the artifact. The message tells you to publish again to that slug.\n\n- The pre-check that runs before an upload now also runs when you update an existing slug with a page over a certain size. Before, it ran only when there were supporting files or removals.\n\n**Why**\n\nPublishing again after an interrupted publish lands on the same artifact instead of creating another one.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}