Tag ImmichFrame chart from upstream release

2026-10-19 21:02:13 +02:00
parent f4c1faf57b
commit 14ef867b5a
2 changed files with 11 additions and 5 deletions
@@ -25,11 +25,13 @@ helm upgrade --install immichframe brunner.ninja/immichframe \
  --values values.yaml
 ```

-The chart version has no `latest` alias. Every successful main-branch workflow
-publishes a unique SemVer version, `0.<run-number>.<attempt>`, so GitOps can pin
-and roll back an exact package. The default upstream image is the chart's
-`appVersion`; `image.registry`, `image.repository`, and `image.tag` can all be
-overridden independently.
+The chart version has no `latest` alias. Git tags follow the upstream
+ImmichFrame release (for example `v1.0.39.0`). Because Helm chart versions
+must be SemVer, the fourth upstream component becomes a prerelease component:
+`v1.0.39.0` publishes chart `1.0.39-0`; a later chart-only commit publishes
+`1.0.39-0-1-g<commit>`. GitOps pins the exact package. The default upstream
+image is the chart's `appVersion`; `image.registry`, `image.repository`, and
+`image.tag` can all be overridden independently.

 Each configured Immich account references an existing Kubernetes Secret. The
 chart mounts its key as a file and writes only `ApiKeyFile` into
@@ -9,4 +9,8 @@ version=${description#v}
 case "$version" in
  *-0-g*) version=${version%%-0-g*} ;;
 esac
+# Upstream uses four numeric components (for example v1.0.39.0), whereas
+# Helm chart versions must be SemVer. Keep the upstream Git tag verbatim and
+# encode its fourth component as a SemVer prerelease identifier.
+version=$(printf '%s\n' "$version" | sed -E 's/^([0-9]+)\.([0-9]+)\.([0-9]+)\.([0-9]+)(-.*)?$/\1.\2.\3-\4\5/')
 printf '%s\n' "$version"