Skip to content

Release Notes

The authoritative, per-release changelog lives in the public meta-tolomeo repository and is generated from the commit history of every release. This page explains how to read it and how releases are versioned.

Changelog

The complete, up-to-date list of features, fixes, and security updates is maintained in the public repository:

Public changelog

CHANGELOG.md

Each entry links to the merge request and commits behind the change, grouped by type: Features, Bug Fixes, and Security.

Versioning

Releases are tagged as <semver>+<YY.MM>, combining a semantic version with the calendar of the release:

  • <semver> — the meta-tolomeo layer version. The minor field increases for new features, the patch field for fixes and security updates.
  • <YY.MM> — the year and month the release was cut (for example, 26.01 is January 2026), matching the cadence of one release every two months shown on the Roadmap.

A tag such as v1.0.0+26.01 therefore identifies both the layer version and the release window it belongs to.

Cadence

meta-tolomeo publishes a maintenance release roughly every two months on each active LTS line. New features land during the feature phase of a line; once a line enters security maintenance, releases carry security updates and critical fixes only. See the Roadmap for the phase and end-of-life date of each line.

See also

  • Roadmap — LTS release lines and maintenance windows