{"version":"2.1.277","anchor":"reserved-artifact-mints-tracked-separately-from-stranded-min","canonical_anchor":"reserved-artifact-mints-tracked-separately-from-stranded-min","heading":"Artifact publishing now tracks reserved slugs separately from stranded ones","tier":"internal","area":"Artifact Publish","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277\/e\/reserved-artifact-mints-tracked-separately-from-stranded-min","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277","markdown":"### Artifact publishing now tracks reserved slugs separately from stranded ones\n\nArtifact publish tracks a new set of reserved slugs alongside stranded ones, improving staleness and overwrite checks\n\n**Unclear.** What a 'mint' is and how an artifact being reserved differs from stranded is not explained.\n\n**What**\n\nThe artifact publish tool now keeps a `reservedMints` set alongside the existing `strandedMints` set. A slug is added to `reservedMints` when a publish attempt reports a `reservedSlug`. Both sets are cleared together at the same reset points and on conflict, and `reservedMints` is also checked when deciding whether an artifact is stale.\n\nA new `neverPublished` outcome is also handled, letting overwrite checks proceed as if the target slug had no prior page.\n\n**Why**\n\nThis gives the artifact publish flow more accurate bookkeeping about which slugs are reserved versus stranded, improving how staleness and overwrite decisions are made when publishing artifacts.\n\n- Area: Artifact Publish\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}