{"version":"2.1.300","anchor":"artifact-publish-edits-gate-frozen-separately","canonical_anchor":"artifact-publish-edits-on-the-publish-call-and-a-deploy-re","heading":"Artifact publish edits get new model guidance, and unclear deploy failures now surface","tier":"notice","area":"Artifacts","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300\/e\/artifact-publish-edits-gate-frozen-separately","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300","markdown":"### Artifact publish edits get new model guidance, and unclear deploy failures now surface\n\nClaude is now told it can send small artifact changes as `edits` on publish, and an unclear deploy failure is no longer hidden by a retry\n\n**Unclear.** Whether this changes when the `publish_edits` option is available is not clear.\n\n**What**\n\nAn artifact is a page Claude Code builds from a file and publishes. Publishing can already take a list of `edits`, pairs of old and new text (`old_str`\/`new_str`). What is new:\n\n- New instructions tell the model it can send small changes as `edits` on the publish call itself, with or without editing the file first. Before, the model always edited the file and then published again.\n\n- A `frozenPublishEdits` value, or a default when it is not set, decides which of two wordings the model gets. The `edits` option is now controlled by this value on its own, rather than being worked out while the tool's input is being prepared.\n\n- Claude Code now records a `publish_edits` field alongside the artifact tool's other recorded settings.\n\n- When publishing goes through `\/deploy\/direct` and an attempt ends without a clear answer, Claude Code remembers that. If the retry also fails, it reports the earlier unclear failure as an error. Before, it returned the last response. The retry message now reads \"ended without a clear answer\".\n\n**Why**\n\nPublishing a small change to an artifact can take fewer steps. A publish that may not have gone through now shows up as an error, rather than being covered by the retry's last response.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}