Skip to content

0.1.3 release record

Status: qualified for signed publication

0.1.3 adds deployment controls for the supported PostgreSQL, MySQL, and SQLite stores while preserving the documented 0.1.x Python API and CLI contract. It also closes the correctness, security, conformance, and release hardening findings identified during the pre-release code review.

Added

  • Explicit expand/contract migration compatibility metadata and writer-quiescence acknowledgements.
  • Credential-free PostgreSQL migration scripts and PostgreSQL/MySQL grant renderers suitable for review before deployment.
  • Read-only startup readiness checks for runtime and retention database lanes.
  • Machine-readable store security profiles and stronger cross-adapter conformance scenarios.
  • A tested SQLAlchemy 2 and async Alembic hosting recipe with separate action and application migration ledgers.

Safety fixes

  • PostgreSQL and MySQL readiness checks now reject excess privileges and unsafe grant delegation authority.
  • Runtime failure cleanup, concurrent execution recovery, verification evidence, mixed item outcomes, and committed operation events now preserve the exact supported semantics under edge conditions.
  • Conformance leakage scans cover unordered collections without unbounded derived references.
  • Release workflow actions are pinned to immutable commits.

Release gates

The signed v0.1.3 workflow must prove that the tag commit is already on main, rebuild and qualify the artifacts, verify exact TestPyPI byte digests, publish the same artifacts to PyPI, and record their provenance in the GitHub release.