From 592de4dcc9958544c805ea011a06d081ed266ce4 Mon Sep 17 00:00:00 2001
From: 0xFEEDC0DE64 <daniel@brunner.ninja>
Date: Mon, 19 Oct 2026 17:27:01 +0200
Subject: [PATCH] Align chart tag with dated asciinema release

---
 README.md | 9 +++++----
 1 file changed, 5 insertions(+), 4 deletions(-)

diff --git a/README.md b/README.md
index dc3d7f8..7f794d2 100644
--- a/README.md
+++ b/README.md
@@ -44,10 +44,11 @@ cluster.
 
 ## Chart releases
 
-Git tags version the chart (`v1.0.0` publishes chart version `1.0.0`). Commits
-after a tag use the unique `git describe --tags --long` version, including the
-commit hash. `Chart.yaml.appVersion` is the exact upstream application image
-tag selected by the chart. The workflow requires `PACKAGE_USERNAME`,
+The upstream image uses a date tag, currently `20260626`. The chart maps it
+to SemVer tag `v2026.6.26`, which publishes chart `2026.6.26`. Later chart
+commits append the `git describe --tags --long` count and hash.
+`Chart.yaml.appVersion` remains the exact upstream image tag. The workflow
+requires `PACKAGE_USERNAME`,
 `PACKAGE_TOKEN`, and `GITOPS_TOKEN` repository secrets; it does not access
 Kubernetes.