Skip to content

ci: name the image's tag in the deploy-stage dispatch #22

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
MehranMazhar merged 1 commit into from
Sep 25, 2026
Merged

ci: name the image's tag in the deploy-stage dispatch #22

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions .github/workflows/docker-build-push.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -178,12 +178,21 @@ jobs:
exit 1
fi

# clutch-deploy pins every image to an exact tag and deploys only what is pinned, so the
# dispatch names the tag this run pushed: metadata-action's type=sha, sha-<first 7 of the
# commit>. clutch-deploy checks that ghcr.io has it and pins it for STAGE only. The mainnet
# validators keep their own pin, which moves only in a planned upgrade.
- name: Name the tag this run pushed
id: tag
run: echo "sha=sha-${GITHUB_SHA::7}" >> "$GITHUB_OUTPUT"

- name: Trigger deploy-stage in clutch-deploy
uses: peter-evans/repository-dispatch@v3
with:
token: ${{ secrets.CLUTCH_DEPLOY_DISPATCH_TOKEN }}
repository: clutchprotocol/clutch-deploy
event-type: deploy-stage
client-payload: '{"set_images": "clutch-node=${{ steps.tag.outputs.sha }}"}'

- name: What this proves, and what it does not
run: |
Expand Down
Loading