From d0d1690a64dd133e195fde7c35539502506b9277 Mon Sep 17 00:00:00 2001 From: "Kostis (Codefresh)" <39800303+kostis-codefresh@users.noreply.github.com> Date: Wed, 16 Nov 2022 05:35:29 +0200 Subject: [PATCH] docs: Added warning about existing tag in semver (#471) Signed-off-by: Kostis Kapelonis Signed-off-by: Kostis Kapelonis --- docs/basics/update-strategies.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/docs/basics/update-strategies.md b/docs/basics/update-strategies.md index 0963a534..499e6c17 100644 --- a/docs/basics/update-strategies.md +++ b/docs/basics/update-strategies.md @@ -77,6 +77,10 @@ The above example would update to any new tag pushed to the registry matching this constraint, e.g. `1.2.5`, `1.2.12` etc, but not to a new minor version (e.g. `1.3`). +!!!warning "A note on the current image tag" + For semver strategy to work, the current application tag must already follow + semver. Otherwise no comparison can happen by the updater. See discussion at [#270](https://github.com/argoproj-labs/argocd-image-updater/issues/270) for more details. + Likewise, to allow updates to any minor release within the major version `1`, use @@ -101,6 +105,8 @@ Image Updater will pick the highest version number found in the registry. Argo CD Image Updater will omit any tags from your registry that do not match a semantic version when using the `semver` update strategy. + + ### latest/newest-build - Update to the most recently built image