Repository navigation
ci(publish): auto-promote to production after release-triggered staging publish - #72
Merged
Merged
Conversation
…ging publish Production was manual-dispatch only. Add a `workflow_run` trigger so that when "Publish to marketplace (staging)" completes successfully AND that staging run was triggered by a GitHub Release (event == 'release'), production auto-promotes the same versions. Preserves the staging-first ordering and the existing safety gates: - manual staging dispatches / dry-runs do NOT promote (not release-triggered) - canonical-repo guard retained - manual workflow_dispatch (with template filter + dry-run) retained - unchanged versions are idempotent 409 no-ops on the control plane Co-Authored-By: Claude Opus 4.8 <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
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.
What
Wire production to auto-promote after a successful, release-triggered staging publish — closing the last manual step in the release flow.
Today:
release: published→ staging publishes (auto); production is manual dispatch only. This adds aworkflow_runtrigger topublish-production.yml:The job only runs the auto-promote path when all hold:
conclusion == 'success'event == 'release'← so manual staging dispatches & dry-runs never promoteobjectstack-ai/templatesManual
workflow_dispatch(template filter + dry-run) is unchanged. The auto path has no inputs → empty filter → publishes all templates (unchanged versions are idempotent409no-ops).Resulting flow
Notes
main(GitHub only firesworkflow_runfrom the default branch).🤖 Generated with Claude Code