v0.9.12 — 2026-08-26

A build whose branch is deleted from origin mid-build (the usual fate of a merged branch) no longer vanishes from the UI and history while it is still queued or running — previously the queue looked stuck although a build was executing.
Triggering a build that is already queued or running for the same commit no longer stacks a duplicate — an impatient double-click on restart now hits the existing build. Re-running a finished build is unaffected.

v0.9.11 — 2026-08-14

At the end of each poll cycle, the local branch refs of the watched repository are fast-forwarded to their state on origin, so build steps that compare a branch with its origin counterpart no longer fail once origin moved on. Only fast-forwards are applied — a branch that diverged from origin or is ahead of it stays untouched. Switched off with watcher.fastForwardLocalRefs: false.
On the artifact index of a failed build, the logs that actually contain the build tool's failure line carry a failed badge — with stdout and stderr stored separately, that points straight at the log worth opening. Logs of a green build are not scanned.

The control token is no longer embedded in the pages — reading them is unauthenticated, so anyone could have picked it out of the HTML. Viewing stays public; the first click on a restart/cancel/delete button asks for the token once (it is in .git/gittally/control-token on the host) and keeps it in the browser.

Changed default: server.bindAddress is now 127.0.0.1 instead of 0.0.0.0, because neither the UI nor the API authenticates read access. Existing .gittally.yml files keep whatever they set; with the managed nginx container, 0.0.0.0 has to be set explicitly.
The control token is accepted in the X-GitTally-Token header only — the token query parameter is gone, as URLs end up in access logs and browser history.
config:print masks git.token; --show-secrets prints it.
Files holding secrets (the Gitea token written by init, the control token) are created with mode 0600 right away instead of being chmod-ed afterwards, the control token is compared in constant time, and git calls pass -- before branch names.
On narrow screens the page title and the repository name are stacked instead of wrapping.

The artifact index also links report pages of directories without an index.html. A directory holding a single page is linked as a directory, so Gradle's --profile report keeps a stable URL although its file name carries the build timestamp.
The permanent 🔗 link now appears on the build it resolves to — the branch's latest green build — instead of on every build of that branch, and on all build tables.
The Current tab gave way to a 📡 link in the artifacts column, shown while a build runs.

init --systemd also installs a nightly Docker cleanup timer (gittally-docker-prune.timer, 02:00 host time): stopped containers and unused images are pruned before the auto builds — like the legacy host, but the per-repository Gradle cache volumes survive.

This release-notes page, linked from the version in the footer.
Mobile: the live indicator collapses to a colored state dot so it no longer squeezes the menu.
The system page highlights critical utilization: the current value of CPU, RAM, and disk used turns orange from 80% and red from 90% of the respective total.

Builds killed by a server shutdown (e.g. a deployment restart) are recorded as interrupted instead of failed, publish a pending Gitea status, and are re-enqueued when the server starts again.

The legacy page names (/index.html, /branches.html, …) answer with permanent redirects to the new routes, so pre-rewrite bookmarks and the redirect from the old host keep working.

The artifact page shows a n failed badge behind links to test reports that contain failures.

Cancelling a build also terminates its auxiliary phases (Docker image build, Gradle cache volume preparation), so the next queued build starts immediately.

Durations no longer flicker while live-updating.
While a build is running or pending, the artifact link shows an hourglass (logs only, so far) instead of the report icon.
Pending builds show their queue wait time in italics; running and finished builds show the pure build time without the wait.

Port of the legacy gitTally bash script to Kotlin/Spring Boot — the first production deployment of the rewrite.

Dual-mode application: CLI (init, status, build, retry, config:print) and HTTP server with this web UI and a JSON API.
Declarative YAML configuration: committed .gittally.yml plus machine-specific overrides and secrets under .git/gittally/.
Builds run detached in git worktrees — the primary checkout is never used for builds.
Docker build containers with automatic image rebuilds and a per-repository Gradle cache volume; works under rootless Docker daemons; git metadata is available read-only inside the container.
Branch watcher with auto-builds (nightly slots), a pull-request gate, and pruning of results, artifacts, and stale worktrees.
Commit statuses reported to Gitea; artifact store with per-branch retention and permanent latest-green links; system metrics page.
Managed nginx/TLS container (Let's Encrypt) for hosts without a reverse proxy; init --systemd generates the service unit.
Self-contained runtime bundle (jlink-trimmed JRE + jar) for hosts without a Java runtime.