0.2.1

Changed

• Pin the shared Gates reusable workflow to 2c3c6acd0a6795768446e925a6137e17357f267a
  (Gates 0.1.2), which publishes the release the workflow on main downloads. No check, policy
  field or receipt format changed; the version increment alone invalidates receipts retained
  under 0.1.1.

Fixed

• Shared Gates 0.1.1 rejects non-automation commit authors before scanning or reusing signed
  evidence, including intermediate commits and merged side branches.

Source distribution, publish = false; no binary artifacts. Required checks passed on the
release commit: common / Security and privacy and real-backends (PostgreSQL 17.6 production
proof with verified TLS). The local gate was green before publication: 129 tests passed, 0 failed,
0 ignored, no skipped or selected-zero lane, plus cargo fmt --all --check and
cargo clippy --workspace --all-targets --locked -- -D warnings.

0.2.0

Added

• Add the local eventlog-file provider with versioned JSONL transactions, process-safe atomic
  groups, durable retry identities, verified blob storage and recoverable privacy rewrites.
  Redacted file-store projections require a complete rebuild before serving new writes; existing
  receipts remain resolvable. File-provider verification and operating limits are documented in
  docs/design/file-provider.md.
• SQLite and PostgreSQL implement ordered atomic append groups with one tenant-scoped
  idempotency identity, actual-content retry matching and transaction-local expectations.
  Required projections and group admission commit or roll back with the entire group.
• Projection and guard contexts can read tenant-scoped blobs inside their current transaction.
  Existing single-stream append entrypoints retain their behavior.

Changed

• Adopt independent common security/privacy gates with signed local evidence and bot delivery.
  Cache Rust proof builds and cancel superseded PR runs while retaining all persistence proof lanes.
• PostgreSQL admits the new group bookkeeping through an additive, physically checked migration;
  previous schema editions remain migratable. Hosted writers require the new table's DML grants.

This source release was published without running gates, tests or binary packaging.

0.1.0

First Eventlog source release: tenant-scoped event streams, aggregates, snapshots and projections backed by SQLite or PostgreSQL.

• Stable guard refusal codes with transactional rollback, plus generic effect evidence and boundary coverage contracts.
• Verified snapshot generations prevent stale cache writes after redaction or erasure; automatic cache failures preserve committed append results.
• Hosted PostgreSQL admission verifies TLS, roles, schema shape, projection migrations and connection budgets.
• Catch-up polls reuse settled connections; public append inputs and PostgreSQL rewrite rules are validated before durable writes.

All four crates are version 0.1.0, licensed under Apache-2.0 and distributed as source (publish = false). Pin the annotated Git tag 0.1.0.

Compatibility: snapshot saves require an observed generation; the legacy unproven save API refuses writes. PostgreSQL snapshot provenance uses an additive migration. Mixed protocol generations require a fenced cutover.

Validation covers both real backends, verified PostgreSQL TLS, formatting, linting, comparative laboratory workloads and restart replay. Laboratory results do not admit a production capacity budget. Public documentation delivery is asynchronous.

See CHANGELOG.md for the complete release contents.

Required CI proof passed on release commit dce9bcdbd0596c0f0756139b859a6ff2d05d8ba8: 98 tests, zero failures/skips, 12 comparative configurations and two restart checks. Exact source, binary and runner identities are retained in the workflow artifact.