Under the hoodTier: how much it should matter to you
2Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
PublishingArea: what it touches
Internal ChangesKind: in v2.1.271,
Internal ChangesSection of the release
What
When publishing content, Claude Code now records a "lane" describing how the source bytes were originally captured — one of "admitted", "confined", "plain", or "pinned" — alongside the existing hash and size checks. It also adds a dedicated step that re-checks, using the method appropriate to that lane, that the source hasn't changed before trusting a cached read of it.
Why
This makes publishing more resistant to publishing stale or tampered content, by re-verifying the source through the right method for how it was originally obtained rather than assuming a cached copy is still valid.
