Follow Discord
Sweep 22 Sep 2026 · 17:19Z Build v2.1.280 501 read Stable v2.1.267 Latest v2.1.280 Next v2.1.280 Feeds RSS JSON llms.txt Unofficial
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.

TierUnder the hoodhow much it should matter to you
Useful2my rating, 1 to 5
Signal2worth watching, 1 to 5
AreaArtifactswhat it touches
KindInternal Changesin v2.1.268,
Group of 2 Under the hood No documentation found

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

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.

Read from
Names in the bundleldxBuild
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 ldx build step actually does, and what consumes the ldxBuild result, is not stated in the finding.

See this entry in the whole of v2.1.268 →

Feedback