{"version":"2.1.267","anchor":"batch-write-messaging-refined-for-version-pinned-writes","canonical_anchor":"batch-write-messaging-refined-for-version-pinned-writes","heading":"Batch-write messaging refined for version-pinned writes","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267\/e\/batch-write-messaging-refined-for-version-pinned-writes","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267","markdown":"### Batch-write messaging refined for version-pinned writes\n\nError message for version-pinned batch writes now says the whole batch is refused, not applied piecemeal\n\n**What**\n\nWhen Claude Code explains why an unsupported batch write can't proceed, it now takes into account whether the batch is version-pinned. For a version-pinned batch, the message says it will only be applied all-or-nothing if the server supports batch writes; otherwise it's refused entirely, since 'a version-pinned batch is never applied one at a time'. This replaces the previous message, which described a one-at-a-time fallback.\n\n**Why**\n\nThis corrects the explanation given to accurately reflect that a version-pinned batch can't be split apart and applied piece by piece, avoiding a misleading description of what happens when the write fails.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}