Group of 4 You'll notice
No documentation found
Database write, delete, and batch-write tools now give specific guidance when a required if_version was left out, backed by a version_required error code
What
- Document/database write and delete tools now give a dedicated error message when a change to an existing document was missing a required
if_version, distinguishing delete, update, and create/default cases with wording like "this delete carried no if_version — nothing was deleted". - The batch-write tool gives the same kind of message, naming the exact write's index and path, and warns that other unpinned writes in the same batch will fail the same way.
- All these messages tell the model to
read_db(or read the document) first, then resend the write withif_versionset. - A new
version_requiredreason (with arequired: truefield) is now returned separately from the genericversion_mismatchreason, backed by a structured error-detail schema (code, kind, limit, version, index, required).
Why This makes "optimistic concurrency" failures (where a document changed since you last read it) much easier to recover from: instead of a generic version-mismatch error, Claude Code now gets a precise explanation of what went wrong and how to fix it, reducing wasted retries on database writes.
Names in the bundleif_version