✨ feat: Add logic to push 'latest' tag for Docker images based on release tags #261
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 pull request updates the Docker image publishing workflow to automatically tag images as
latestwhen the current release matches the latest GitHub release. The workflow now determines if the pushed tag is the most recent and, if so, pushes an additionallatesttag alongside the versioned tag.Key changes to the Docker publish workflow:
Automated tagging logic:
preparejob to compare the current tag with the latest GitHub release tag using the GitHub CLI (gh). If they match, apush-latestflag is set totrue. (.github/workflows/docker-publish.yml)push-latestvalue is now output from thepreparejob for downstream steps to use. (.github/workflows/docker-publish.yml)Image publishing enhancements:
push-latestistrue, the workflow adds thelatesttag to the image alongside the version-specific tag. (.github/workflows/docker-publish.yml)Workflow cleanup:
.github/workflows/docker-publish.yml)