Let Publish Images be started by hand - #198
Merged
Merged
Conversation
The automatic chain is CI -> Publish Images -> Deploy Delta, linked by workflow_run. When GitHub throttles webhook delivery during an Actions incident, no workflow_run event fires: CI never chains to Publish, so no image exists, so Deploy Delta -- which does take a workflow_dispatch -- has nothing to deploy. main sits undeployed with no way to force it, which is what happened today. workflow_dispatch is served by the REST API rather than the webhook pipeline, so it survives that failure mode. Scalene's deploy is already reachable this way and shipped fine this afternoon while this repo could not. Publishing stays restricted to main. The dispatch is pinned to the main ref, and an explicitly supplied SHA -- the one input not already constrained -- is checked for ancestry on main before anything is built, so no dispatch can produce an image Deploy Delta would release from a commit that never landed. Co-Authored-By: Claude Opus 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.
Why
The automatic chain is CI → Publish Images → Deploy Delta, linked by
workflow_run. During today's Actions incident GitHub throttled webhook delivery, so noworkflow_runevent fired: CI never chained to Publish, no image was ever built, and Deploy Delta — which does accept aworkflow_dispatch— had nothing to deploy.mainhas been sitting undeployed since 16:16 UTC with no way to force it through.workflow_dispatchis served by the REST API rather than the webhook pipeline, so it stays available when that path is throttled. Scalene's production deploy is already reachable this way and shipped fine this afternoon, while this repo could not.What
Adds a
workflow_dispatchtrigger topublish.ymlwith an optionalshainput, defaulting to the tip ofmain.Publishing is still restricted to main
Two guards, because an image published here is what Deploy Delta releases to production:
mainref in the job'sif.sha— the only input not already constrained by that — is checked for ancestry onmainvia the compare API before anything is built.identical(it's the tip) andbehind(an earlier commit on main) pass; anything else means the commit lives on another branch and the run fails.Testing
YAML parses and the trigger/input/concurrency keys resolve as intended. The dispatch path itself gets exercised immediately after merge — deploying the backlog from #195 is the reason this is going in today.
🤖 Generated with Claude Code