It would be great if the released versions would follow Semantic Versioning. So you could determine if the release is stable or not.
My use case:
I’m using Renovate to automatically update the image tag for my Helm Charts.
Unfortunately the “next” images are released with a “stable” tag (without pre-release identifier at the end). So Renovate can not distinguish stable releases from unstable ones.
I think it would be beneficial to add this because:
If you would use pre-release identifiers like 1.0.0-beta or 1.0.0-rc.1 everyone could see at a glance which state the releases have.
I’m not using next or latest.
I pin the tag to a specific version. Preferably to the last stable version.
If a new version is released Renovate creates a Pull Request to update to this version.
Usually this happens only for stable versions, but in this case the pre-release versions are not distinguishable from stable versions.
So it would help, if unstable versions would have an appropriate pre-release identifier.
Ah I see that makes more sense, Where does Renovate get the data from is it just from Dockerhub or can it can pull from Github where releases are tagged as Latest or Pre-Release? It is not a tool I am familiar with, We are always open to tweaks though.
@rob_otter I have had some success by setting "pinDigests": true in the renovate.json file and then setting the compose file to use the latest tag, as the renovate will then base it’s updates on eg. n8nio/n8n:[email protected]:3ec353a93b512f6ca9c1b4203e13593dafe866b677ab6f446e6707decef52a36 and if the digest changes it will make new PR for the latest tag, but it still stands that this versioning scheme on dockerhub at least is not intuitive.
So the digest renovate pins for you in a compose will resolve itself automatically to the manifest in question and then the docker engine will resolve to it’s compatible arch within the manifest sha256.