releases
Stable means pinned
A RivetHub stable release is a set of exact tags,
digests, and checksums — not a floating latest.
the pin file
What "stable" means here
Every fetch the installers make from RivetOS goes through one pin
file, distro/pins/stable.json in the RivetOS repository:
rivetos_tag- the exact RivetOS tag bare-metal node installs clone
image- the GHCR agent image for
--docker, preferred in digest form (@sha256:…) pgvector_image- the Postgres 16 + pgvector image for
--dockerdatahub installs rivet_ca_sha256- checksum of the pinned CA library
hub_helper_version- version of the
rivethub-hubhelper (currently0.1.0)
When you install from the stable channel, you get exactly those artifacts. A new release is a new pin file, reviewed and tagged.
current channel state
Current channel state
The machine-readable channel file is served at
releases/latest.json.
It includes the runtime channel, installer checksums, and an apps object for Linux, Windows and Android. Each app entry has version, file, sha256 and sizeMB (rounded decimal MB). Downloads use https://rivethub.io/releases/<file>; the local guide and Apps page read this feed.
local.sh- The full laptop setup: hub, agent runtime, and local UI. Published at
https://get.rivethub.io/local.sh; SHA256 inlocal_sh_sha256. datahub.sh- Dedicated datahub. Published at
https://get.rivethub.io/datahub.sh; SHA256 indatahub_sh_sha256. The helpers it fetches are pinned by their own*_sha256fields inpins/stable.json, as the datahub guide explains. node.sh- Enroll an agent node. Checksum in
node_sh_sha256.
changelog
Changelog
Release notes and the changelog live with the source: the distro
repository (pins/README.md documents each pin field) and
the RivetOS runtime repository, documented at
rivetos.dev. Consult the current release feed and source release notes for the exact versions available.