From 5bbe422734b3321d8ebb5aa501cc2d91d8ede227 Mon Sep 17 00:00:00 2001 From: mhoennig Date: Wed, 26 Aug 2026 13:35:17 +0200 Subject: [PATCH] Visible mid-merge builds and dedup'd triggers (v0.9.12) Deployment bundle: the prune protection for queued/running builds and the manual-trigger dedup. Co-Authored-By: Claude --- build.gradle.kts | 2 +- src/main/resources/templates/releases.html | 10 ++++++++++ 2 files changed, 11 insertions(+), 1 deletion(-) diff --git a/build.gradle.kts b/build.gradle.kts index 1d8bee6..d92aa4e 100644 --- a/build.gradle.kts +++ b/build.gradle.kts @@ -12,7 +12,7 @@ group = "de.hoennig" // bump at least the patch version for every deployment — and only then, not per commit — // so the UI footer (BuildProperties), --version and the release notes identify what is // actually running; a deployment bundles whatever was committed since the last one -version = "0.9.11" +version = "0.9.12" java { toolchain { diff --git a/src/main/resources/templates/releases.html b/src/main/resources/templates/releases.html index 26ba63c..42f4fc6 100644 --- a/src/main/resources/templates/releases.html +++ b/src/main/resources/templates/releases.html @@ -7,6 +7,16 @@
+

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