From 28c7a4ad15a572c2a370c7593d4573b1f398fc75 Mon Sep 17 00:00:00 2001 From: 0xFEEDC0DE64 Date: Mon, 19 Oct 2026 17:31:53 +0200 Subject: [PATCH] Align chart tag with application 0.2.0 --- .gitea/workflows/container.yml | 2 +- README.md | 6 ++++-- 2 files changed, 5 insertions(+), 3 deletions(-) diff --git a/.gitea/workflows/container.yml b/.gitea/workflows/container.yml index 86ab8d8..4fbf719 100644 --- a/.gitea/workflows/container.yml +++ b/.gitea/workflows/container.yml @@ -55,7 +55,7 @@ jobs: fi - name: Package and publish Helm chart - if: gitea.ref == 'refs/heads/main' || startsWith(gitea.ref, 'refs/tags/v') + if: gitea.ref == 'refs/heads/main' env: CHART_VERSION: ${{ steps.version.outputs.version }} COMMIT_SHA: ${{ gitea.sha }} diff --git a/README.md b/README.md index cd7ba43..1d090da 100644 --- a/README.md +++ b/README.md @@ -117,8 +117,10 @@ Per-process operational counters and active gauges should be summed across repli The Gitea Actions workflow in `.gitea/workflows/container.yml` builds and pushes `registry.brunner.ninja/feedc0de/immich-sync`. Every release receives an immutable image tag containing its full Git -SHA. The same run packages the chart with that SHA as `appVersion`. Chart versions come from `git describe`: tag -`v1.0.0` produces chart `1.0.0`; a later commit produces a unique version such as `1.0.0-1-g41627ab`. +SHA. The same run packages the chart with that SHA as `appVersion`. The +repository tag follows the application's `CMakeLists.txt` version: `v0.2.0` +produces chart `0.2.0`; later chart commits produce unique versions such as +`0.2.0-1-g41627ab` through `git describe`. The workflow deliberately loads the completed image into the Docker engine and pushes it with a separate plain `docker push`. It does not request provenance attestations, SBOM manifests, or OCI referrers, retaining compatibility