Releases
How Harthelm is versioned, what a release contains and how to move between releases.
Every Harthelm release has one version, X.Y.Z, for everything in it: the Helm chart, the five container images and
the hart command line. Chart 1.1.0 installs images 1.1.0, and the hart of release 1.1.0 reports 1.1.0.
| Release | Date | Highlights |
|---|---|---|
| 1.5.0 | 2026-10-19 | Uploads from a team's custom domains to public S3 hosts; the doctor as a console page; nightly backups skip a managed service that is still starting; the installation id and the order of a fresh install; Strict-Transport-Security on the console; the dump log's tls and tls_verify; a longer install guide. |
| 1.4.0 | 2026-10-15 | Browser hosts for RabbitMQ and S3: single sign-on to RabbitMQ's management UI, public S3 stores; in-cluster TLS for S3; safer S3 backups; the restore runbooks as a release asset. |
| 1.3.0 | 2026-10-14 | Valkey, MariaDB, RabbitMQ and S3 object storage as managed services; ${{ services.<name>.secret }}; in-cluster TLS for managed services. |
| 1.2.2 | 2026-10-13 | Only a verified email goes onto a commit, in terminals, hart exec and the editor. |
| 1.2.1 | 2026-10-13 | The waiting page keeps going; services wake without waiting for the editor; commits in the editor name the right person; terminals at their real size; old Git remotes work again. |
| 1.2.0 | 2026-10-12 | hart smoke; registry pull secrets for team namespaces; a quieter licence check at start. |
| 1.1.0 | 2026-10-12 | Licences; Harthelm's own names for availability and provider definitions; the importer removed; the source bundle. |
| 1.0.4 | 2026-10-12 | Open-source notices in the console, the server, the chart, hart and the images; the editor without GitHub Copilot; clearer console labels. |
| 1.0.3 | 2026-10-11 | The night drain also puts stopped services to sleep; hart ws wake --wait waits for every target; a Restart keeps the run stage going. |
| 1.0.2 | 2026-10-11 | Run no longer waits for a service it needs that is failing; versions are reported correctly; mirror.sh for air-gapped installs. |
| 1.0.1 | 2026-10-11 | Restorable platform dumps; first Argo CD sync without the pre-migration dump. |
| 1.0.0 | 2026-10-11 | The first stable release. |
These docs describe v1.5.0.
Versions
Versions follow semantic versioning. A patch release (1.0.2 → 1.0.3) carries fixes and
small additions and needs no manual step: its database changes only add, and its chart takes the values of the
release before. Minor and major releases say in their notes what changed and what to do.
Pre-releases (1.1.0-rc.1) are candidates for testing. They are published apart from the releases, so an installation
that follows the newest chart never picks one up by accident.
What a release contains
| Part | What |
|---|---|
| Helm chart | harthelm-X.Y.Z.tgz, also in the OCI registry as oci://<your registry>/charts/harthelm, version X.Y.Z. The packaged values.yaml pins every image by digest. |
| Images | Five images, each for linux/amd64 and linux/arm64: the server (core, router and the jobs), the workspace agent, the tools image of the backup jobs, the base image of workspaces and services, and the editor image. |
images.txt | Every image an installation can start, one per line with its digest, including the PostgreSQL operator and operands, the images of the other built-in managed services (since 1.3.0) and cert-manager. |
mirror.sh | Copies every image of images.txt into your own registry, for air-gapped installs. Since 1.0.2. |
hart | Archives for macOS and Linux on amd64 and arm64, hart_X.Y.Z_<os>_<arch>.tar.gz, with hart_X.Y.Z_SHA256SUMS. See Install hart. |
| Source bundle | The source code of the open-source components in the images that their licences require, as the OCI artifact <your registry>/harthelm/sources:X.Y.Z, and harthelm-X.Y.Z-sources.txt with its digest and index. See Open-source components. Since 1.1.0; release candidates have none (since 1.4.0). |
| Restore runbooks | harthelm-restore-X.Y.Z.tar.gz with harthelm-restore-X.Y.Z.tar.gz.sha256: the scripts that put a managed service's backup back into an instance. See Backups and restore. Since 1.4.0. |
Releases are not published on a public registry yet. Your vendor or administrator tells you where the chart and the
archives come from; these docs write <your registry>.
Check which version runs
hart versionhart version prints its own version, the API version it speaks and, when it knows your installation, the server's.
The server's version is also in every API answer, in the header Harthelm-Version, and at GET /api/v1/version. hart warns when the
two differ in the major or minor number; update hart then. Servers of 1.0.0 and 1.0.1 report dev instead of their
version.
Upgrade and roll back
Upgrade with helm upgrade and the new version:
helm upgrade harthelm oci://<your registry>/charts/harthelm --version 1.4.0 -n harthelm-system -f my-values.yamlBefore an upgrade the chart checks the cluster and dumps the platform database; database changes only add things, so the previous release still runs on the upgraded database. To roll back, upgrade to the previous version the same way. Upgrades explains each step, and Argo CD how to pin a version there.
Read the notes of every release between yours and the new one: they list changed values and anything to do.