{"version":"2.1.273","anchor":"artifact-publish-gains-a-reservedpre-assigned-slug-path","canonical_anchor":"artifact-publish-gains-a-reservedpre-assigned-slug-path","heading":"Artifact publish gains a reserved\/pre-assigned slug path","tier":"internal","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273\/e\/artifact-publish-gains-a-reservedpre-assigned-slug-path","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273","markdown":"### Artifact publish gains a reserved\/pre-assigned slug path\n\nPublishing an artifact can now target a slug that was reserved ahead of time\n\n**What**\n\nThe function that publishes an artifact now accepts a pre-reserved slug (the short identifier used in an artifact's URL), letting a publish attach to that slug specifically. Its telemetry also now records `is_redeploy`, `has_base_version`, and a `reserved` flag when this path is used.\n\n**Why**\n\nThis supports publishing to a slug that was set aside in advance, such as for a redeploy of an existing artifact, rather than always generating a fresh one, and lets Anthropic track how often that happens.\n\n- Area: Artifacts\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}