Release v0.1.61 · block/schemabot

Highlights

Destructive changes to tables another open PR owns are flagged — when a plan drops or destructively alters a table that a different open pull request already claims, the plan comment attributes the change to that PR instead of presenting it as unowned, and every comment an apply acts on carries the disclosure. (#1017)
Auto-plan is scoped to the schema a pull request actually proposes — discovery compares the PR's schema files against the default branch, so a pull request stacked on a stale base no longer plans changes it never made. (#1016)
Command rejections lead with the database's operators — a rejected command tells you who can authorize it first, instead of burying the operator list under the reason. (#960)
Lint warnings render like issues, and long lists fold — warning formatting matches the issues block, and oversized lists collapse instead of flooding the comment. (#959)

A local drive heartbeats the row it actually owns — lease heartbeats are bound to the claimed row, so a drive can no longer refresh a lease it no longer holds. (#915)
A deferred cutover is held — when an operator defers the cutover, the apply waits for the operator instead of proceeding on its own. (#978)
VSchema-only work dispatches to remote data planes — work operations that carry no copy task are dispatched over gRPC like every other operation, so VSchema-only changes complete on remote engines. (#961)

PostgreSQL dialect nucleus in the shared store core — the store core carries a dialect seam that both MySQL and PostgreSQL back ends render through. (#1010)
Public PostgreSQL store constructor — embedders can construct a PostgreSQL-backed store directly. (#1012)
Lease-guarded joined DML is portable — the operation store's lease-guarded updates and joined UPDATEs render through the dialect rather than assuming MySQL syntax. (#1011, #1009)

The tasks database index widened. On MySQL, the self-bootstrapping schema check applies this automatically at startup. On PostgreSQL, the bootstrapper creates missing tables but does not alter existing ones — operators running a PostgreSQL-backed store should apply the index change before deploying this version.

Full Changelog: v0.1.60...v0.1.61