{"version":"2.1.265","anchor":"new-approval-record-checks-for-pinnededit-database-writes","canonical_anchor":"new-approval-record-checks-for-pinnededit-database-writes","heading":"New approval-record checks for pinned\/edit database writes","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265\/e\/new-approval-record-checks-for-pinnededit-database-writes","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265","markdown":"### New approval-record checks for pinned\/edit database writes\n\nCertain database writes now require a matching prior approval, tracked per session, before they're allowed\n\n**What**\n\nSome database writes that first read back the stored document \u2014 such as string-replace style edits, or writes pinned to a specific version using `if_version` \u2014 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.\n\n**Why**\n\nThis 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.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}