chronomemory Changelog¶

All notable changes to the chronomemory ESDB engine. Available on PyPI.

[0.2.4] — 2026-06-23¶

O(1) WAL append (_append_wal): replaced the O(n²) full-rewrite strategy with a direct open("a") append. WAL format is unchanged; all existing WAL files are fully compatible.
Stale .wal.tmp cleanup on open(): any .wal.tmp left by a crashed ≤ v0.2.x process is silently removed before acquiring the write lock.

conftest.py CI reliability hook: guarantees the CI "Check for test failures" step has valid pass/fail data even when Python crashes during JUnit XML write on Windows Server 2025.

Cross-platform single-writer file lock (events.wal.lock) — prevents concurrent writes.
Chain validation warning on open() — RuntimeWarning if WAL hash chain is broken.
WAL auto-compaction threshold (max_wal_events) — keeps WAL size bounded.
__del__ safety net — ResourceWarning if store is GC'd while open.
open() idempotency — double-open is a no-op.
EsdbBridge per-operation lock release — releases write lock immediately after each call.
18 new production-hardening tests.

_WriteLock._try_clear_stale() Windows OSError handling for stale lock detection.

EsdbId unified to String-typed ID — full bidirectional Python↔Rust WAL replay. All existing WAL files remain compatible.

Rust↔Python record schema alignment — RecordKind, RecordStatus, EdgeType now serialise with Python-compatible lowercase strings. Fixes query(kind="fact") on Rust-written WALs.
Serde aliases for Python vocabulary ("deprecated", "tombstone", etc.).

Production hardening: file locking, auto-compaction, __del__ safety, startup performance test.

Hash compatibility: compact JSON separators in WAL hash computation — aligns Python json.dumps with Rust serde_json; fixes cross-language SHA-256 chain verification.