Latest release changed to 0.18. then switched back to 0.19 #220
Description
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.