chore(ci): resume use of latest tag for stable image #113
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.
I intentionally stopped publishing a
:latest
tag back on April 1st. It was not intended to be an April Fool's joke, but rather a cleanup to best practices of not using that tag. However, the old images did not expire, so the old:latest
continues to exist, confusing both users and our website's image discovery code.I suppose it turned out to be a long lived April Fool's joke after all!
This resumes the publishing of the tag, ensuring it matches the
:stable
tag, and only on theucore
image. There will be no:latest
for nvidia, zfs or testing images, norfedora-coreos
orucore-hci
.