Follow Discord
Sweep 06 Nov 2026 · 01:32Z Build v2.1.319 537 read Stable v2.1.311 Latest v2.1.318 Next v2.1.319 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.277 ·

Artifact publishing now tracks reserved slugs separately from stranded ones

Artifact publish tracks a new set of reserved slugs alongside stranded ones, improving staleness and overwrite checks

Group of 2 Under the hood Internal Changes
JSON All of v2.1.277
Under the hoodTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
Artifact PublishArea: what it touches
Internal ChangesKind: in v2.1.277,
Internal ChangesSection of the release

Unclear What a 'mint' is and how an artifact being reserved differs from stranded is not explained.

What

The 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.

A new neverPublished outcome is also handled, letting overwrite checks proceed as if the target slug had no prior page.

Why

This 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.

How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtWhat a 'mint' is and how an artifact being reserved differs from stranded is not explained.

See this entry in the whole of v2.1.277 →

Feedback