feat(deploy): add workflow_dispatch for manual binary deploys - #148
Merged
Conversation
Enables manual re-deployment of any release tag without needing a new Release workflow run. Resolves the dead-end where re-running Release fails (release already exists) and Deploy Binary only fires on successful Release completion. Co-Authored-By: Claude Sonnet 4.6 <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.
Problem
Deploy Binary is only triggered by a successful Release workflow run. When a release already exists (v0.7.1), re-running Release fails at "Create GitHub Release", so Deploy Binary never fires. This leaves production stuck on an older binary despite the release artifacts being present.
Fix
Add `workflow_dispatch` trigger with a `version_tag` input. A new `Resolve release tag` step selects between the dispatch input and the `workflow_run.head_branch` value so both paths share the same download/deploy steps.
Test plan
🤖 Generated with Claude Code