GitVersion: [Bug] Docker latest points to alpha
Our build scripts were using the :latest label in Docker to execute GitVersion with the following command
docker run --rm -v "$(pwd):/repo" gittools/gitversion:latest /repo
Something has changed recently where that command no longer outputs the JSON response, but instead it’s printing out the visual tree of the repo. We’re hard coding back to 5.11.1 now to fix things, but I figured I’d report this. I don’t know what’s of more concern, if the default behavior is changing to this tree output, or that the latest is pointing at a pre-release version. Shouldn’t it point at the latest stable version?
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 17 (12 by maintainers)
The previous tags for 6-alpha1 are still there https://hub.docker.com/layers/gittools/gitversion/6.0.0-alpha.1/images/sha256-6291d5e167a97cee1b5f4c579d6b27138a055da25547170ec486007fa062daf1?context=repo
With the release of 5.12.0, the
latesttag is again pointing to version 5.x.In that case we can agree on setting
:latesttag as latest stable. In that case the user of the:latesttag should be aware of the possibility of breaking changes in major versions. And as a recommendation is to use a specific version instead of the:latest. We need to update the readme on DockerHub with this recommendation. I will have to re publish the:latesttag with the 5.x version and remove those with:latest-6.0, and adapt the build scripts accordingly.Ok then, I will remove the
:latesttag from DockerHub, adapt the CI code, and update if needed thereadmeon DockerHub