ci: name the image's tag in the deploy-stage dispatch - #22
Merged
Merged
Conversation
clutch-deploy now pins every image to an exact tag and deploys only what is pinned (clutch-deploy #103). So the dispatch after an image build carries the tag that build pushed, sha-<first 7 of the commit>, as client_payload.set_images. clutch-deploy pins it for stage only. The mainnet validators keep their own pin, which moves only in a planned upgrade. This merge rebuilds the image, because the workflow lists its own file in its paths. The stage validators then run that build of the same code. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
1 participant
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.
clutch-deploy now pins every image to an exact tag and deploys only what is pinned (clutchprotocol/clutch-deploy#103). This PR makes the deploy-stage dispatch name the tag the build just pushed,
sha-<first 7 of the commit>, asclient_payload.set_images. clutch-deploy checks that ghcr.io has the tag, commits the pin to itsmain, and deploys. No other image moves.Merge order. Merge this only after clutch-deploy#103 is merged and its first deploy is green. Before that, clutch-deploy ignores the payload and deploys every
latestimage, which today would ship the undeployed GasFree treasury images.What the merge does. The image workflow lists its own file in its paths, so the merge rebuilds the image from the same code. Its dispatch is the first real test of the new flow: the clutch-deploy run should show a
pinjob with adeploy(stage): pin ...commit, then a green deploy.🤖 Generated with Claude Code