From bc0b0311158fefbf1fd898ddcadfd47bd5be8cde Mon Sep 17 00:00:00 2001 From: Erich Blume Date: Thu, 19 Feb 2026 18:09:26 -0800 Subject: [PATCH] Document version tracking convention in review-services Container image tags are decoupled from upstream app versions; service-versions.yaml tracks the upstream app version. Co-Authored-By: Claude Opus 4.6 --- docs/how-to/knowledgebase/review-services.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/docs/how-to/knowledgebase/review-services.md b/docs/how-to/knowledgebase/review-services.md index 4716bbf..f07a017 100644 --- a/docs/how-to/knowledgebase/review-services.md +++ b/docs/how-to/knowledgebase/review-services.md @@ -1,6 +1,6 @@ --- title: Review Services -modified: 2026-02-16 +modified: 2026-02-19 tags: - how-to - maintenance @@ -62,6 +62,10 @@ Same as ArgoCD, but also check for new chart versions in the mirrored chart repo 3. If upgrading, update the version and dry-run: `mise run provision-indri -- --tags --check --diff` 4. Follow [[add-ansible-role]] patterns for role changes +## Version Tracking Convention + +The `current-version` field in `service-versions.yaml` tracks the **upstream application version**, not the container image tag. For hybrid services, the container image tag (e.g., `v1.0.0`) is decoupled from the contained app version (e.g., `v1.10.1`). This allows container rebuilds (base image updates, build fixes) without implying an upstream version change. + ## Marking a Service as Reviewed After reviewing, edit `service-versions.yaml` (repo root) and update the service entry: