Versioning and compatibility
The draft software-version and format-generation axes, intended stable-release policy, and required updates for format-breaking changes.
View authoritative sourceCurrent status
Avelune currently has no stable codec, container, or public API. The public software tree uses 0.x versions until the project intentionally declares a stable compatibility line.
Separate version axes
Two version axes are deliberately separate:
-
Software version — Cargo crates, CLI, web player, and tooling. During
0.x, incompatible API changes may occur in a minor release. -
Format generation — identifiers such as
ALV1andALA1. “1” currently means Draft Generation 1; it does not mean that the format has been frozen or promised permanent compatibility.
Intended stable-line policy
Once a stable major line is declared, the intended policy is:
-
patch: compatible fixes only;
-
minor: compatible features and encoder improvements; existing valid streams remain decodable;
-
major: incompatible public API, codec/container syntax, or decoded-semantics change.
A new stable major may replace the previous one or coexist with it. Long-term maintenance of old major lines will be decided explicitly rather than promised in advance.