Release · 4 October 2026
GNIZDO 0.1.0: releases now have version numbers
Until now, a GNIZDO production deploy could be identified by a timestamp and a source commit, but the product itself did not have a formal version number. Version 0.1.0 changes that.
Every formal GNIZDO release now has a product version and a release note. We keep that version separate from the deployment ID and the exact source commit, because they answer different questions: what product release is this, which deployment is serving it, and which code produced it.
Why this matters
- When something changes, we can say exactly which GNIZDO version introduced it.
- Support and debugging can refer to the same release instead of comparing screenshots or timestamps.
- Future API and product changes have a visible history instead of disappearing into deployment details.
What changed for inventory monitoring?
Nothing. This release does not change how GNIZDO reads channel catalogs, checks evidence or evaluates inventory. It makes the product itself traceable, so later changes can be explained clearly.
From here
New formal releases will appear on this page in plain language. The repository changelog remains the technical record; News is the human version.