Skip to content

Commit 0ca1d7b

Browse files
sspreitzercrenshaw-dev
authored andcommitted
docs: add a precise description on helm chart prerelease version comparison. Fixes argoproj#21818 (argoproj#22724)
Signed-off-by: Sascha Spreitzer <[email protected]> Signed-off-by: Michael Crenshaw <[email protected]> Co-authored-by: Michael Crenshaw <[email protected]>
1 parent 070270e commit 0ca1d7b

File tree

1 file changed

+5
-0
lines changed

1 file changed

+5
-0
lines changed

docs/user-guide/tracking_strategies.md

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -23,6 +23,11 @@ Helm chart versions are [Semantic Versions](https://semver.org/). As a result, y
2323

2424
[Read about version ranges](https://www.telerik.com/blogs/the-mystical-magical-semver-ranges-used-by-npm-bower)
2525

26+
!!! note
27+
If you want Argo CD to include all existing prerelease version tags of a repository in the comparison logic, you explicitly have to add a prerelease `-0` suffix to the version constraint. As mentioned `*-0` will compare against prerelease versions in a repository, `*` will not. The same applies for other constraints e.g. `>=1.2.2` will **not** compare prerelease versions vs. `>=1.2.2-0` which will include prerelease versions in the comparison.
28+
29+
[Read about prerelease version comparison](https://github.com/Masterminds/semver?tab=readme-ov-file#working-with-prerelease-versions)
30+
2631
## Git
2732

2833
For Git, all versions are Git references but tags [Semantic Versions](https://semver.org/) can also be used:

0 commit comments

Comments
 (0)