{"version":"2.1.268","anchor":"artifact-publish-runs-a-new-post-publish-ldx-build-step","canonical_anchor":"artifact-publish-results-can-include-a-new-ldxbuild-segmen","heading":"Artifact publish runs a post-publish 'ldx build' step","tier":"internal","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268\/e\/artifact-publish-runs-a-new-post-publish-ldx-build-step","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268","markdown":"### Artifact publish runs a post-publish 'ldx build' step\n\nPublishing an artifact now runs an ldxBuildAfterPublish step and returns its result as ldxBuild in the tool output.\n\n**Unclear.** What the ldx build step actually does, and what consumes the ldxBuild result, is not stated in the finding.\n\n**What**\n\n- 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.\n\n- 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.\n\n**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.\n\n- Area: Artifacts\n- Names: `ldxBuild`\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}