Harthelm 1.2.2
What changed in Harthelm 1.2.2: an email address goes onto a commit only when your sign-in provider verified it.
Last updated 2026-10-19
Released 2026-10-13. API version 0.11.1, unchanged. A patch release without breaking changes and without database migrations: upgrade as usual.
helm upgrade harthelm oci://<your registry>/charts/harthelm --version 1.2.2 -n harthelm-system -f my-values.yamlChanged
- Only a verified email goes onto a commit. Harthelm sets your name on every commit you make, in a Harthelm
terminal, with
hart exec, in a run's steps and in the editor of your browser window. Your email is added only when your sign-in provider verified it. Without a verified email, Git takes the email from the workspace's global Git config (git config --global user.emailin the editor's terminal), else the workspace owner's, and the owner's only when it is verified too. In 1.2.1 this applied to the editor only; terminals used the email unverified. See Start from a repository. - The console's notice in a colleague's terminal now says that commits there carry their name and, if verified, their email.
Harthelm 1.3.0
What changed in Harthelm 1.3.0: Valkey, MariaDB, RabbitMQ and S3 object storage as managed services next to PostgreSQL, a managed service's secret as its own variable, in-cluster TLS for managed services.
Harthelm 1.2.1
What changed in Harthelm 1.2.1: a waiting page that keeps going, services that wake without waiting for the editor, Git commits that name the right person, terminals at their real size, and old Git remotes that work again.