Align chart tag with application 0.2.0
Publish image, chart, and GitOps promotion / Test and publish immutable artifacts (push) Successful in 28s
Publish image, chart, and GitOps promotion / Test and publish immutable artifacts (push) Successful in 28s
This commit is contained in:
@@ -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 }}
|
||||
|
||||
@@ -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
|
||||
|
||||
Reference in New Issue
Block a user