Skip to content

ETLantic 0.41.0

Latest
Latest

Choose a tag to compare

View all tags
@github-actions github-actions released this 01 Aug 01:34
v0.41.0
bd2f47f

[0.41.0] - 2026-07-31

Adopter summary
Who must act Anyone pinning etlantic==0.40.x or plugins with <0.41
Breaking Dependency floor becomes etlantic>=0.41.0,<0.42 (CP3 durable-work line)
Upgrade pip install 'etlantic==0.41.0' and matching plugins / medallantic==0.41.0. See Migration 0.40 → 0.41
Rollback Re-pin 0.40.0 minors together; re-validate
Security CP3 durable coordination + fencing/outbox evidence; not a production multi-tenant isolation claim (0.43)

Added

  • CP3 DurableWorkStore / MemoryDurableWorkStore: accept/outbox, cancel,
    leases/fencing/heartbeat/release, attempts, checkpoint CAS, effects,
    replay/repair/backfill plans, preview TTL/staleness/shadow, admission
  • Optional SQLModel durable provider + migration 002_durable_cp3
  • FastAPI optional durable_work injection, dual-write submit, /v1/durable/*
  • Durable conformance/chaos scripts and chaos matrix evidence
  • What's New / Migration / Exit Gate / Findings for 0.41; ADR-018 Accepted

Changed

  • Official package versions align at 0.41.0; plugins require
    etlantic>=0.41.0,<0.42
  • Durable-work hardening requires fenced checkpoint CAS; cancellation expires
    leases and blocks heartbeat/CAS; control-plane cancellation is durable-first,
    and CP1 compensates when durable acceptance fails
  • SQLModel durable storage now covers read-only plan/explain/replay paths;
    FastAPI profile resolution fails closed; Safe I/O preserves numeric zero for
    read budgets and lock timeouts
  • Supported security release line is 0.41.x
  • GitHub Actions use the current checkout, uv (setup-uv@v9.0.0), Java,
    provenance, SARIF, and artifact action majors; CI runs on uv 0.12.0 and
    covers Airflow 2.11.1 and 3.2.1 (the resolvable final 2.x line and current
    3.x line)

Security

  • Stale fencing tokens cannot publish terminal state or advance checkpoints
  • Unknown external effects fail closed without reconciliation evidence
  • Durable input snapshots, replay diffs, preview reasons, and CLI diagnostics
    are redacted; secret and Safe I/O failures cannot be bypassed by
    CONTINUE/SKIP policies
  • Explicit docs boundary: CP3 ≠ production multi-tenant
Assets 38
Loading