From f46e5f572977c1e54616080a7d7083ec782ccf8c Mon Sep 17 00:00:00 2001 From: Niklas Ye Date: Tue, 1 Sep 2026 22:38:41 +0200 Subject: [PATCH] Set the chart's placeholder version to 0.9.3 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Cosmetic, and done anyway, for the same reason as 477454e: these two lines decide nothing about what is published — `helm package --version --app-version` now sets both from the tag, so they are not even read during a release — but a tree heading for v0.9.3 that says 0.9.2 tells its reader something false. The comment above them was rewritten to stop naming a specific version. It described the tree as "heading for v0.9.2", which is exactly the kind of line that has to be edited every release and is therefore the kind that goes stale. It also said nothing that publishes looks at these fields, which only became literally true in 69fcc24 when the sed was replaced by helm's own flags. Claude-Session: https://claude.ai/code/session_01S7R4gWTz5wh5xCY4nCSJjN --- charts/terdut-server/Chart.yaml | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/charts/terdut-server/Chart.yaml b/charts/terdut-server/Chart.yaml index ed2a2bf..91f0d05 100644 --- a/charts/terdut-server/Chart.yaml +++ b/charts/terdut-server/Chart.yaml @@ -6,13 +6,14 @@ type: application # released values. .gitea/workflows/release.yaml rewrites both from the git tag when it # publishes, so the chart version always equals the app version. # -# They are kept in step with the tag anyway. Being read is the only thing these two -# lines do -- nothing that publishes looks at them -- and a tree heading for v0.9.2 that -# says 0.9.0 tells its reader something false. That is what they said until 2026-09-01, +# They are kept in step with the tag anyway. Being read is the only thing these two lines +# do -- `helm package --version --app-version` sets the published values from the tag and +# never consults these -- and a tree heading for a numbered release that states an older +# number tells its reader something false. They said 0.9.0 and "latest" until 2026-09-01, # through two releases. # # appVersion and image.tag in values.yaml no longer agree, and that is not an oversight: # image.tag stays "latest", which is what a local install actually pulls. appVersion is # metadata and drives nothing. -version: 0.9.2 -appVersion: "v0.9.2" +version: 0.9.3 +appVersion: "v0.9.3"