Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.
Sign upAdd "v1 latest" tag to Docker images #3098
Comments
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
|
Aaaaand my "latest" targeting deployments are now broken with v2 being published. |
brian-brazil
added
kind/enhancement
priority/Pmaybe
labels
Dec 8, 2017
This comment has been minimized.
This comment has been minimized.
|
It seems unlikely at this stage that there will be further 1.x releases, so this is obsolete. In general if you use "latest" and things break, you get to keep both pieces. |
brian-brazil
closed this
Feb 2, 2018
This comment has been minimized.
This comment has been minimized.
lock
bot
commented
Mar 22, 2019
|
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
lock
bot
locked and limited conversation to collaborators
Mar 22, 2019
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
sandersaares commentedAug 21, 2017
The Docker image at https://hub.docker.com/r/prom/prometheus/tags/ currently has version-specific tags and latest/master tags but nothing that means "latest from the v1 branch".
This is desirable for automation scenarios that will pull a new Docker image on deploy. As there are breaking changes between v1 and v2, if one day "latest" points to v2 then those automated deploys will fail for no too-obvious reason.
If switching to v2 requires an explicit change in the Docker tag, the reason for any breakage after such an action is obvious. Therefore I request a "latest-v1" style tag, in addition to the existing ones.