{"version":"2.1.285","anchor":"artifact-publish-retries-and-merge-tracking","canonical_anchor":"artifact-publish-retries-and-merge-tracking","heading":"Artifact publishing retries more reliably and reports when it merged over a newer version","tier":"notice","area":"Artifacts","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285\/e\/artifact-publish-retries-and-merge-tracking","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285","markdown":"### Artifact publishing retries more reliably and reports when it merged over a newer version\n\nArtifact publish retries honour retry-after with jitter and retry relay outages, and the result now warns when it merged over a newer version\n\n**Unclear.** What a merged version means for the artifact a reader sees is not settled.\n\n**What**\n\nArtifacts are files Claude Code publishes so they can be viewed or shared. This release changes how publishing works:\n\n- Retries now wait according to the server's `retry-after` hint plus a small random delay, and a relay-unavailable response also triggers a retry. Before, the delay only came from `retry-after`, with a cap.\n\n- Claude Code now keeps track of its own version and any merged version of a publish.\n\n- A publish response can include `merged_over`, which describes the base version, the live version, and the files that were changed or left out.\n\n- When a publish was merged over a newer version, the result shown to Claude now says so, lists the changed and removed files, and tells it to re-read them before editing.\n\n- File reads now include a `title`, and the relay request can ask for compression with a `compress` option.\n\n**Why**\n\nPublishing should fail less often during brief server outages. The merged-over note stops Claude from overwriting files that changed elsewhere, because it is told to read the newer content first.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}