Latest release changed to 0.18. then switched back to 0.19
Opened this issue · 2 comments
Althought nothing new seems to be published / committed I can see that latest release changed to 0.18. then switched back to 0.19
It happens sometimes and causes my cicd to regenerate my images. Which is a bit useless. I certainly can refuse downgrade on my side but there must be an issue on your repo causing that double switch.
It happened like 1 hour ago.
Again the 14th December.
And The 5th December
12 November.
Etc
Is this a faulty deployment strategy ?
GitHub failure ?
The other repo I track doesn't do that.
happened again today
at arround 9H00 UTC : v0.19.0 => v0.18.0
and reswapped at arround 10H00 UTC : v0.18.0 => v0.19.0
That sounds like a GitHub failure. I have seen many scripts scraping GitHub get weird/inconsistent results over time.
I'm not sure how you are scraping versions, but I think we've had better success with git ls-remote than anything else (https://github.com/docker-library/docker/blob/c0a2a6d85dab907b5a9349f7a25eb7eadbbfa4ea/versions.sh#L32).