Release catalogue

Updates

This page lists what the release catalogue actually holds: the version, the recorded status, the size and the publication time of each build, with the notes the release carries.

Published releases

Scope of this page: the Windows (x64) builds on the Stable channel. Other platforms and channels are not listed here, and the download page shows what is offered for the platform you are on.

No verified releases are published yet, so there is nothing to update to. The release catalogue holds no entry for this platform on this channel. Nothing has been published, so nothing is listed, and this page does not fill the gap with a release history that did not happen. When GrowLeafy publishes a build that can be attributed to a signer, it appears here with its own version, status, size, date and notes.

How updates work

An update is a signed artefact and a decision, not a silent file replacement.

Signed, and verified against a pinned key

A client checks an update against the GrowLeafy trust anchor it already holds. An update signed by any other authority is refused rather than installed. The public key is readable at the trust anchor.

Channels

Releases sit on a channel. Stable is the default channel a normal installation follows; a beta channel exists for builds that are not the default yet. A channel is a choice, not a promise, and this page names the one it is showing.

A release can be revoked

When a release is revoked, new downloads for it stop immediately, and installed machines are told to move to a supported build. They are told, not broken: revocation withdraws an authorisation, it does not disable a computer.

Verify the SHA-256 printed on the download page against the file you received.
The installation guide covers registration and activation, not just copying files.
Platform verdicts, including what is not built yet, are on the compatibility page.
If an update is refused or a machine is stuck, the support team can read the server-side record of it.