Changelog

Release notes live with the releases, not here, so there is one copy of them and it cannot go stale.

No OpenMila release has been published yet. The repository is in early development; the first Linux beta will appear on the releases page.

How the version numbers work

OpenMila follows Mila's releases. Each OpenMila version is a port of one Mila version, named <mila version>+port.<n>: 1.9.5+port.1 is Mila 1.9.5, first port build. Features, models and engine pins track upstream; the port adds platform code, not features.

The Mila version currently matched is v1.9.5-beta.2, recorded in UPSTREAM_VERSION, and OpenMila's own version is 1.9.5-beta.2+port.3. Because the feature set comes from upstream, the question "what changed" splits in two: what Mila changed, and what the port changed.

Mila's own release notes, with its feature list, requirements and changelog, are kept verbatim in the repository at docs/upstream/MILA-README.md and refreshed on every upstream sync.
The upstream files the port modifies are listed in CHANGES.md.
How far each feature has got on each system is the parity table, re-measured on every upstream sync.

Pre-releases

A version with a suffix, such as 1.9.5-beta.2+port.0, is published as a GitHub pre-release. The AppImage's own updater has a beta channel with a pre-release guard, so a beta is offered only if you asked for betas. A .deb install does not update itself and is pointed back to the releases page, because that belongs to the package manager.

What every release contains

An AppImage and a .deb for Linux, a portable zip for Windows, a SHA256SUMS file, an SBOM and a build provenance attestation. The download page has the commands to check all of it.