What probably matters to youSection of the release
What
write_db batch operations can now include an if_version on each entry, individually pinning specific documents to an expected version so the whole batch fails if any pinned document changed since it was read.
A new delete db_op is added to write_db, working alongside set, update, str_replace, and it too can carry an if_version constraint.
If the number of entries in a batch changes after approval (entries added or removed), the write is now rejected with "this batch no longer lists the writes that were approved (entries were added or removed)".
Batches now track a version pin per entry (entryPins), not just one overall pin, and a server that doesn't support batch writes with version pins at all now gets its own explicit error.
Version-mismatch errors are clearer: when the document's current version is known, the error tells you the new version number to plan against; when it's unknown or deleted, it tells you to check whether the document still exists, and for deletes says there's nothing left to do while for other operations it suggests re-creating with a plain set. The error also names which specific write in the batch was stale.
Why
This lets tools safely make several conditional writes at once instead of just one: if any pinned document was modified elsewhere since being read, none of the batch is applied, and the error message tells you exactly which write conflicted and what to do about it, instead of silently overwriting concurrent edits.
