Follow Discord
Sweep 12 Nov 2026 · 20:38Z Build v2.1.323 540 read Stable v2.1.311 Latest v2.1.322 Next v2.1.323 Feeds RSS JSON llms.txt llms-full.txt Unofficial
The last run did not finish v2.1.323 no changelog was produced for this release

Claude Code v2.1.281 ·

Artifact publish: per-file precondition conflicts (precondition_failed)

Artifact patch publishes can send per-file checks, and a conflict now reports which files differ from what was expected

Under the hood Improvements
JSON All of v2.1.281
Under the hoodTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
ArtifactsArea: what it touches
ImprovementsKind: in v2.1.281,
ImprovementsSection of the release

Unclear The finding does not say what the extra upload parameter does.

What

When Claude Code publishes changes to an artifact as a patch (only the changed parts), it can now send a precondition for each file. A precondition is a check saying "only apply this if the file still looks the way I expect."

If the server refuses with a conflict (HTTP status 409) and the reason precondition_failed, Claude Code now works out which files caused it. For each conflicting path it records:

  • the expected sha256, a fingerprint of the file contents Claude Code thought was there
  • the actual sha256, the fingerprint of what the server really had

The conflicting paths are also reported in usage data as conflict_paths. Upload calls take one extra parameter as well.

Why

A failed publish can now name the exact files that changed underneath it, instead of failing as a whole with no detail. This makes it easier to see which files someone else edited in the meantime.

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 doubtThe finding does not say what the extra upload parameter does.

See this entry in the whole of v2.1.281 →

Feedback