Source Intelligence
Follow Discord

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

← All of v2.1.239 Home All releases ←olderv2.1.238 v2.1.240newer→
Claude Code v2.1.239

Clearer rules for force-publishing an artifact

Use it now
Useful2 Signal2
Artifacts

The force publish option now warns about in-page saves and says the server may refuse.

force
What

The force option's description now covers the case where a newer version was saved from inside the artifact page itself, not just another session publishing, warns never to force purely to get past a conflict, and notes the server may refuse a force over an in-page save.

Details
  • The client-side stale-version check that could abort a publish with stale_version_guard or stale_version_guard_seeded was removed from this path.
  • The read performed before publishing now passes session credentials.
Evidence

unless it refuses force over a version saved from inside the page

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

Related

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.

See this entry in the whole of v2.1.239 →