{"version":"2.1.295","anchor":"artifact-publish-guard-gains-diff-aware-stale-version-handli","canonical_anchor":"artifact-publish-guard-gains-diff-aware-stale-version-handli","heading":"Republishing an unchanged or outdated artifact gets a more detailed check","tier":"internal","area":"Artifacts","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295\/e\/artifact-publish-guard-gains-diff-aware-stale-version-handli","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295","markdown":"### Republishing an unchanged or outdated artifact gets a more detailed check\n\nWhen you republish an artifact that matches the live version or is behind it, Claude Code now gives its outdated-version check more detail about the attempt\n\n**Unclear.** The message shown when such a publish is refused was not seen, so it is not known how this changes what you see.\n\n**What**\n\nClaude Code has a check that runs when you publish an artifact that is identical to the version already live, or that is known to be older than it. That check used to receive only the content being published. It now also receives:\n\n- whether the content can be compared line by line with the live version\n\n- whether the publish is \"page only\", meaning it comes with no files, copies, removals or metadata options\n\nThe record of each publish now also notes whether the content was identical to the live version.\n\n**Why**\n\nWith this extra detail, the check can treat a resubmission of the page alone differently from one that carries files or other changes. It can also see whether the new content can be compared against what is live.\n\n- Area: Artifacts\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}