feat(ci): auto-deploy to production after Release succeeds on main#98
Merged
feat(ci): auto-deploy to production after Release succeeds on main#98
Conversation
Adds a workflow_run trigger on Release completion (branch=main, conclusion=success). Previously push-to-main only published the `latest` release asset; an operator had to then manually dispatch production-deploy.yml. Now the sequence is automatic. - Manual workflow_dispatch still works (re-deploy a specific tag). - workflow_run fires on every Release run; the job's `if:` gates on conclusion=success so failed builds don't promote. - DD_RELEASE_TAG falls back to 'latest' when inputs aren't set (workflow_run has no inputs). Co-Authored-By: Claude Opus 4.6 (1M context) <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.
Summary
Push-to-main now auto-deploys to production after a successful Release run. Previously only
latestwas published and an operator had to dispatchproduction-deploy.ymlby hand.workflow_runtrigger onReleasecompletion,branches: [main]github.event.workflow_run.conclusion == 'success'— failed builds never promoteworkflow_dispatchstill works for re-deploying a specific tag (v0.2.0rollback, etc.)DD_RELEASE_TAGfalls back tolatestwhen no input is providedRollout note
Once merged, the next push to main will:
Releasebuilds + publisheslatestProduction Deployfires automatically, pullslatest, STONITHs the old prod VM, brings up the new one atapp.devopsdefender.comTest plan
workflow_dispatchpath still works manually with an explicitrelease_tag🤖 Generated with Claude Code