Release notes

oxi follows PEP 440 versioning: 0.1.0a* → 0.1.0b* → 0.1.0 stable.

Beta

• v0.1.0b4 — production-feedback cut (saturate closes the loop, ship_recovery rescues failed tasks)
• v0.1.0b3 — cutover-enabling cut (memory backend, ship_recovery filter, infra, first project adapter)
• v0.1.0b2 — polish + supply-chain + observability
• v0.1.0b1 — first beta cut

Alpha

• v0.1.0a6
• v0.1.0a5
• v0.1.0a4
• v0.1.0a3
• v0.1.0a2
• v0.1.0a1
• v0.0.0 — pre-alpha snapshot

Versioning policy

See semver-contract.md for the full versioning contract. TL;DR: alpha releases (a*) may break adapters; beta releases (b*) freeze the adapter protocol within a minor; stable (0.1.0) freezes the public surface for the lifetime of the minor.

Authoring rule

One file per release: v0.1.0.md, v0.2.0.md, etc. Each file has exactly one headline change per anti-patterns §1.