Describe the release
Product ID, channel, version, publication state, release notes, artifact metadata, and integrity information.
Downloads + releases
Release truth before the download button.
Developer, Candidate, and Stable are deliberate promotion states. A public acquisition link appears only after a real artifact has approved version metadata, release notes, integrity information, and an official distribution URL.
Manifest-backedMachine-readable release state stays separate from marketing copy.
Integrity-awareEvery published artifact carries its SHA-256, byte size, architecture, version, and signature state.
No fabricated linksUnpublished products remain visibly in development instead of exposing placeholder installers.
Product fleet
Current release state.
These surfaces report only what the repository currently declares. The absence of a download button is intentional when a verified public artifact does not exist.
Loading the release authority.
No unverified public installer is linked. A missing installer link is a release-safety state, not a broken page. The canonical API is authoritative; legacy static manifests remain available for compatibility.
Distribution architecture
Metadata first. Artifacts second.
The release contract separates what update clients need to know from the binary packages themselves. That keeps version checks deterministic and prevents the public HTML from becoming an accidental source of release truth.
Store the artifact
Approved versioned installers and packages are intended to live in Cloudflare R2 without coupling binary storage to page markup.
Check deterministically
Applications can compare channel metadata without scraping the website or guessing which file is current.
Promotion channels
A build existing does not make it a release.
Developer, Candidate, and Stable represent increasingly strong distribution commitments. Promotion remains an explicit, audited release decision.
Fast-moving engineering
Internal and closely controlled validation builds.
Controlled validation
Authenticode-verified artifacts distributed to a defined testing audience after product-specific gates pass.
Supported public builds
Explicitly promoted artifacts with public acquisition, release notes, version metadata, and integrity checks.
Release notes
Follow the milestone before the installer.
Company updates explain current product and validation work while manifests remain the machine-readable source for published release state.