{"version":"2.1.273","anchor":"artifact-publish-tracks-whether-copied-source-files-survive","canonical_anchor":"artifact-publish-tracks-whether-copied-source-files-survive","heading":"Artifact publish tracks whether copied source files survive a resume","tier":"internal","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273\/e\/artifact-publish-tracks-whether-copied-source-files-survive","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273","markdown":"### Artifact publish tracks whether copied source files survive a resume\n\nPublishing an artifact now records whether copied source files still match what was approved\n\n**What**\n\nWhen publishing an artifact, Claude Code's publish tool can include \"copies\" \u2014 files copied into the artifact from another source. On resuming a publish, it now compares a hash of each copy's path, slug, path, and version against what was originally approved. The result, a true\/false value, is attached to the `artifact_publish_resume` telemetry event as `copies_carried`.\n\n**Why**\n\nThis lets Anthropic detect when copied source files have changed or gone missing between when a publish was approved and when it actually resumes, which matters for keeping published artifacts consistent with what a user agreed to.\n\n- Area: Artifacts\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}