From 0428cf67372d6859966a7ee37dd88571aaf5b25b Mon Sep 17 00:00:00 2001
From: mhoennig <michael@hoennig.de>
Date: Sat, 29 Aug 2026 10:18:21 +0200
Subject: [PATCH] Config files declare their GitTally version (v0.9.18)

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
---
 build.gradle.kts                           |  2 +-
 src/main/resources/templates/releases.html | 17 +++++++++++++++++
 2 files changed, 18 insertions(+), 1 deletion(-)

diff --git a/build.gradle.kts b/build.gradle.kts
index 1bfc012..b0cf80e 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.17"
+version = "0.9.18"
 
 java {
     toolchain {
diff --git a/src/main/resources/templates/releases.html b/src/main/resources/templates/releases.html
index 86ccfd0..6ec2c1e 100644
--- a/src/main/resources/templates/releases.html
+++ b/src/main/resources/templates/releases.html
@@ -7,6 +7,23 @@
     <div th:replace="~{fragments :: nav(${view})}"></div>
     <div class="panel release-notes">
 
+        <h2>v0.9.18 <span class="muted">— 2026-08-29</span></h2>
+        <ul>
+            <li>A configuration file can declare which GitTally it is written for, so a version
+                that renames or drops a key says so instead of silently ignoring what it no longer
+                understands:
+                <code>gitTally: { version: { since: "0.9.18", below: "2.0" } }</code>.
+                <code>since</code> is enforced — both against a GitTally that is too old and
+                against a file written before the version in which the configuration format last
+                changed incompatibly, which GitTally knows about itself. <code>below</code> is a
+                release marker and only warns, so an unmaintained value can never stop a build.</li>
+            <li>The reach follows the file: the machine and project configuration abort the start
+                naming the file and the way back, an incompatible configuration committed on a
+                branch fails only that branch's builds. A file that declares nothing keeps working,
+                and <code>gittally init</code> writes the current version into the config it
+                generates.</li>
+        </ul>
+
         <h2>v0.9.17 <span class="muted">— 2026-08-29</span></h2>
         <ul>
             <li><strong>Fixed:</strong> a page left in the background — a phone tab switched away