Repository navigation
Releases: zanminwang/axton
Release list
v0.5.8
0.5.8 (2026-10-29)
⚠ BREAKING CHANGES
- capable native/PostgreSQL backends default to eight sequential Mutations per transaction. Infrastructure failure rolls back the current group; set protocol5.experimentalMutationGroupSize to 1 for per-member durability.
Performance Improvements
Miscellaneous Chores
- release 0.5.8 (b94892d)
v0.5.7
v0.5.6
v0.5.5
v0.5.4
v0.5.3
v0.5.2
v0.5.1
v0.5.0
AXTON 0.5.0 replaces the superseded engines with the Rust-owned protocol-5 runtime. One Client owns one physical SQLite file and one Stream. Rust manages durable increasing Mutation batches, retries, the delivery queue, atomic complete-unit apply, settlement and reactive notifications; SDKs perform network effects through the existing binding protocol.
Breaking upgrade
- Regenerate client and backend interfaces with the 0.5.0 CLI and use matching 0.5.0 packages.
- Use fresh SQLite files and a fresh PostgreSQL framework namespace. Old formats are refused unchanged; this release supplies no in-place conversion or compatibility bridge.
- Remove public StoreIdentity, generic Load, Query once/refresh/invalidate/cache, row stamps and store hooks. Published Model/Mutation history remains supported.
Bootstrap remains finite, durable and resumable. Query/Fetch perform fresh reads with null-cursor snapshots; they store by default, support store:false, and cannot replace current protected Stream authority. Returning Models does not automatically track them. Local transactions, optimistic companions and independently settled Mutations remain.
See the protocol, adoption guide and accepted implementation and measured limits.
0.5.0 (2026-10-08)
⚠ BREAKING CHANGES
- simplify AXTON to the Rust-owned protocol-5 engine
Features
- simplify AXTON to the Rust-owned protocol-5 engine (5443978)