Don't tag RCs as latest #3702
Open
Don't tag RCs as latest #3702
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
There was a problem hiding this comment.
For production deployments (i.e. in docker-compose.yml) I think this is potentially dangerous as you might unintentionally end up with a newer (incompatible) version. I’m fine with changing the tag to latest for the other config files, but I’d recommend keeping the current versioned tags for production configs.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a proposal which is supposed to minimize merge conflicts and make dependency management easier. By only tagging stable release container images with
latestwe are skipping the tedious work of updating references to the last stable release which often leads to merge conflicts.