Push latest tag for docker/compose #6553
Closed
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
Signed-off-by: Andrew Rabert <ar@nullsum.net>
There was a problem hiding this comment.
Hello @nvllsvm ! First of all, thank you for the interest and the PR, but I will have to decline because it's more complicated than that. Since we have also release candidates, it's not every image that we want to be tagged as latest.
This has to be integrated in the release process, and is implemented in #6641.
Please feel free to evaluate the PR
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.
Tag and push the
latesttag when building and releasingdocker/composeimages.Resolves #6106
Resolves #6006
Partly resolves #4287