ci(verifier): also tag and push :latest on release#723
Merged
Conversation
the verifier release workflow only pushed the version tag, so dstacktee/dstack-verifier:latest was stale (stuck at 0.5.4). add :latest to the pushed tags so every release keeps it current.
Contributor
There was a problem hiding this comment.
Pull request overview
Updates the verifier release GitHub Actions workflow so Docker Hub’s :latest tag is updated on every verifier release, preventing latest from drifting behind the most recent version.
Changes:
- Publish the verifier image with both the version tag and the
latesttag during release builds.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
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
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.
Problem
The verifier release workflow only pushes the version tag (
dstacktee/dstack-verifier:${VERSION}), so:latestis never updated. As a resultlatestis stale — it still points to the old0.5.4image (digest3f36162…), which fails verification on certain attestations and also predates the request-field fix in #722.Fix
Add
:latestto thetags:list of the build-push step so every release keepslatestcurrent.Rollout for 0.5.11
After merge, re-pushing the
verifier-v0.5.11tag re-runs the workflow. The build is reproducible (SOURCE_DATE_EPOCHpinned to the commit timestamp), so the0.5.11digest staysa000ade…andlatestis pushed pointing to the same image.