Follow Discord
Sweep 10 Nov 2026 · 02:18Z Build v2.1.322 539 read Stable v2.1.311 Latest v2.1.322 Next v2.1.322 Feeds RSS JSON llms.txt llms-full.txt Unofficial
HomeReleasesv2.1.268entry #184

Claude Code v2.1.268 ·

Artifact publish runs a post-publish 'ldx build' step

Publishing an artifact now runs an ldxBuildAfterPublish step and returns its result as ldxBuild in the tool output.

Group of 2 Under the hood No documentation found Internal Changes
JSON All of v2.1.268
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
Internal ChangesKind: in v2.1.268,
Internal ChangesSection of the release

Unclear What the ldxBuild segment displays to the user or what triggers it is not stated.

What

  • After a successful artifact/live-doc publish, if the artifact registry module is available, Claude Code now runs a new ldxBuildAfterPublish step (passing slug, files, bornLive status, reseeded flag, signal, and credentials), alongside the existing step that binds born-live working copies.
  • The result of this step is returned as a new ldxBuild field in the publish tool's output, and the tool result now appends an ldxBuildSegment built from it.

Why This adds a build step after publishing so live docs get built automatically as part of the publish flow, and surfaces the build result directly in the tool output for visibility.

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 the ldxBuild segment displays to the user or what triggers it is not stated.

See this entry in the whole of v2.1.268 →

Feedback