What did you do?
I'm sure I'm not the only one that is using prom/prometheus:latest for many of my projects, and yesterday when a bug release for 2.53.4 was released, it also overrode the docker image flag, which broke all the deployments I manage.
Would it be possible to have either a new docker hub tag "stable" (which points to latest stable v3 image) or use latest for latest 3.x release?
Most likely people that are still running v2.x will manually update the tagged releases anyways.
What did you expect to see?
No response
What did you see instead? Under which circumstances?
System information
No response
Prometheus version
Prometheus configuration file
Alertmanager version
Alertmanager configuration file
Logs
What did you do?
I'm sure I'm not the only one that is using
prom/prometheus:latestfor many of my projects, and yesterday when a bug release for 2.53.4 was released, it also overrode the docker image flag, which broke all the deployments I manage.Would it be possible to have either a new docker hub tag "stable" (which points to latest stable v3 image) or use latest for latest 3.x release?
Most likely people that are still running v2.x will manually update the tagged releases anyways.
What did you expect to see?
No response
What did you see instead? Under which circumstances?
System information
No response
Prometheus version
Prometheus configuration file
Alertmanager version
Alertmanager configuration file
Logs