DockerHub releases do not have versioned tags anymore
kba opened this issue · comments
The last versioned release was v2.47.4, we do generate latest from master but not for the releases.
Thx for providing the new version. Could you fix the CI deployment so that the previous and current versions are available as tags? Currently we cannot use the new version. Working on the 'latest' tag for stable versions is not so optimal.
I will rebuild, tag and push manually now and fix the CI afterwards, so you are able to update asap.
It's now fixed, both the Dockerhub and GHCR images are properly tagged automatically. Thanks for the reminder @markusweigelt
And we will use tagged releases as the base for ocrd_all from now on, to make them easier to debug.
Nice and thank you very much for the quick response. In the version overview, there are a few versions in between that look somewhat cryptic, e.g.v2.57.0-1-g9a3bc0e5. What about those? Can they be used? Are those bugfix versions?
Nice and thank you very much for the quick response. In the version overview, there are a few versions in between that look somewhat cryptic, e.g.
v2.57.0-1-g9a3bc0e5. What about those? Can they be used? Are those bugfix versions?
They were the states of master in between releases (version + commit hash). Since 2.57.2, releases should only be deployed for tagged commits. I will remove them from DockerHub.