Update docker-publish.yml to use semver labels for images #2489
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
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.
Minor change: the current workflow (which I added very recently) labels images only with the literal git tag. This change instead labels them with the semver version (without leading
v) which is the more typical Docker convention. E.g. a commit taggedv3.15.12will build an image labeled3.15.12,3.15,3, andlatest.This was the intended behavior in #2479 (and I described this there) but I misunderstood the docs for the
docker/metadata-actionGH Action so the current behavior is actually different from what I intended. This PR should fix that.