Try it free

Releases

Release notes

What shipped, what was fixed, and what is known not to work. A release note listing only improvements is telling you half the story.

builtsigned published withits known limits migrationsrun verified you choose to install rollback every release names its own known limits a release note that lists only what was fixed is a release note that is hiding something rollback is a supported operation, not an exception

How releases work

A release is a single signed bundle containing the images, the migrations and these notes. Every bundle names its predecessor, and one that does not follow your installed version is refused rather than applied — migrations are ordered and applying them out of sequence produces a schema nobody designed.

The upgrade procedure is documented.

Every release names its known limits

Alongside what changed and what was fixed, each release names what is known not to work. Where a device class cannot be verified, where a vendor API does not expose a field, where a control is partial rather than structural — it is written down before you meet it.

Subscribing

Release notes are published here and included in every bundle. If you would rather be told, email support and we will add you — one message per release, nothing else, and unsubscribing is one line back.

Security releases

Security fixes ship as their own release with the advisory attached, and are called out rather than folded into a feature bundle.

If you reported it, you are credited in the notes unless you would rather not be.

Try the current release

Thirty days read-only. Every release note names what is known not to work.