Anthias moves to calendar versions, starting with 2026.05.0

Anthias releases are now numbered by the calendar: the year, a two-digit month and a patch number. 2026.05.0 is the first, and it follows 0.20.5. You'll see the new number on System info, and the update notice now only appears when a newer release has been published.

Its git tag is v2026.05.0. To pin a player to it, choose "tag" at the installer's version prompt and enter v2026.05.0.

The version and the update notice

On System info, "Anthias version" shows the release, such as v2026.05.0, with the short commit hash in brackets under it. It used to show the branch and the commit, such as master@a1b2c3d.

"Update available" appears next to the version when a newer release has been published, and links to the latest release on GitHub. The player looks for a new release once a day. Before, Anthias compared your commit with the newest commit on your branch, so a player installed from master was told to update after any change landed there, release or not. The notice is no longer in the navigation bar, where people had complained on the forum since 2025 that it never went away. From July 2026, when the newest release on GitHub was a WebView release, the check failed on players older than Anthias 2026.07.1.

For developers

In GET /api/v2/info, anthias_version changes from branch@hash, such as master@a1b2c3d, to the release followed by the short hash in brackets: v2026.05.0 (a1b2c3d). On a branch other than master or main, the branch name follows the hash: v2026.05.0 (a1b2c3d, my-branch). up_to_date now compares the player's release with the latest published release.

If a script reads anthias_version: it no longer contains @. Take the release from the text before the first space, and the commit hash from inside the brackets.