You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
ArtifactsArea: what it touches
ImprovementsKind: in v2.1.265,
ImprovementsSection of the release
What
Some database writes that first read back the stored document — such as string-replace style edits, or writes pinned to a specific version using if_version — now must match a prior approval recorded earlier in the same session. This is tracked in a new map called dbWriteOpSights. If no matching approval record exists, or the recorded operation or version doesn't match what's being written, the write is refused with a new error.
Why
This closes a gap where a write could otherwise happen without the approval that was supposed to govern it, ensuring a write only proceeds when it matches what was actually approved.
