SemVer with build metadata

[marksie1988]

Hi All,

Im thinking about amending our release workflow, when i do this I will be adding -rc for staging and also +20251020 for any new builds of the same version. so we would end up with versions like this:

1.0.0
1.0.0+20251020
1.1.0-rc
1.1.0-rc.1
1.1.0-rc.1+20251020

I see that by default it would work with 1.0.0 and no annotation is needed to accept this. Then for staging i add the annotation with x.x-0 which will tell it to accept release candidates for staging.

What its not clear is if it will also accept images that have the build metadata by default +20251020 so that any new builds of any of the images are automatically updated.

Does anyone know if that will be accepted or if there is a specific annotation that is required?

Note this is a new process we are working on and is not fully planned yet so if there is some miss-understanding or a better way to do the tagging im open to recommendations.

Thanks
steve

[chengfang]

argocd-image-updater uses github.com/Masterminds/semver/v3, which fully complies with SemVer 2.0.0 specification. So all these variants of versions are accepted and the build metadata like +20251020 is ignored during precedence comparison. Also see

argocd-image-updater/registry-scanner/pkg/tag/semver.go

Lines 5 to 9 in 2c92bc8

	// semverCollection is a replacement for semver.Collection that breaks version
	// comparison ties through a lexical comparison of the original version strings.
	// Using this, instead of semver.Collection, when sorting will yield
	// deterministic results that semver.Collection will not yield.
	type semverCollection []*semver.Version

for additional sorting

[marksie1988]

Thanks, so for example I have:

1.0.0
1.0.0+20251020

1.0.0 was released first, patches were applied to the docker OS but that app stays at 1.0.0 so we release 1.0.0+20251020, how would argocd-image-updater handle this?

Would it go for the newest image from that version? Or would it just randomly pick one?

The issue I have is I don't want to bump my API version because of OS patches and I also need the ability to have this work for -rc

I may be overcomplicating it as this is quite a new thing for us.

[chengfang]

according to the above semverCollection type, 1.0.0+20251020 will be picked as the most recent version.