Updated latest tag Behaviour #52
Closed
Conversation
This file contains hidden or 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
torbrenner
force-pushed
the
refactor/updateLatestTagBehaviour
branch
from
d9a1bf5 to
07ba708
Compare
Open
|
Tested this and got warnings that suggest it is not working as intended: https://github.com/samply/docker-metadata-action-temp-test/actions/runs/15817783589 Alternative implementation in #53 |
|
Screenshot of the warnings as I think logs are deleted at some point: |
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.
Currently, the latest tag is always added to the images from the repositories default branch.
With this change, the latest tag will only be updated when pushing a git tag matching the semantic versioning scheme.