Skip to content

Anvil 0.6.22

Choose a tag to compare

@fakoli fakoli released this 10 Nov 21:47
· 94 commits to main since this release
78a5f61

Anvil 0.6.22 brings the Kanban workflow and scoped concurrent execution into a compatible schema-26 release, including the existing schema-23 bundle-withdrawal lineage. It also repairs the concurrent SQLite checkpoint race found during 0.6.21 validation. Sources: PR #258, PR #259, and PR #260.

  • Kanban stages follow native Anvil transitions, with guarded approvals, review and closure dispositions.
  • Scoped execution supports bounded bulk authorization and claim-bound command evidence. Acceptance retains its proof and human-approval gates.
  • Native schema migration checks active task and bundle custody in both the projection and canonical log, keeps consistent private backups, and preserves event history. Empty existing projections cannot bypass custody admission.
  • Coordinator-only withdrawal closes unused pristine planned bundles without changing their member tasks or deleting history.
  • Side-effect-free schema probes retry complete captures when a checkpoint removes a WAL or changes the database header. Persistent errors still refuse after three attempts.

This release uses schema 26 and discovery API 24. Upgrade idle State stores through anvil migrate state; preview is the default and --yes applies. Preserve active workers and refresh loaded clients through their owning workflows. See migration guidance. The held v0.6.21 tag remains unchanged; its PyPI publisher was cancelled before upload.

The 15 ms ledger-latency target was not consistently met. Hundreds or thousands of executing containers remain unqualified. A source release does not itself deploy the Web UI, upgrade fleet clients, migrate live State, or repair historical project graphs.

Private migration snapshots use streamed copies with content verification. Arbitrary large WAL/replay histories remain unqualified. Concurrent local-to-Git event-format conversion remains unqualified (MIG-1); stop all writers and retained backend handles before that separate conversion. Schema-only migration preserves event formats.