Rollout — staging dispatch workflow#23
Merged
Merged
Conversation
Adds `.github/workflows/rebuild-on-dispatch-staging.yml`, mirroring the existing production dispatch workflow but checking out `dev`, building with `PUBLIC_ENVIRONMENT=staging`, and deploying via `wrangler deploy --env staging`. A single `product-release-published` dispatch from a product repo now refreshes both environments in parallel. Matches the per-environment-file convention already in place for `rebuild-nightly.yml` / `rebuild-nightly-staging.yml` and `deploy-production.yml` / `deploy-staging.yml`. Note on routing: `repository_dispatch` workflows only fire from files on the repo's default branch (`main`). This file becomes active only after the next dev → main rollout — captured as a comment in the file header. Motivation: the bare-SemVer integration test on 2026-05-13 surfaced that staging was not refreshed by product-release dispatches, so a new release on a draft-only product (e.g. pipeline-test-fixture) required a manual `workflow_dispatch` on deploy-staging.yml to verify on staging. This closes that gap. Co-Authored-By: Claude <noreply@anthropic.com>
…-staging feat(ci): staging counterpart of rebuild-on-dispatch.yml
This was referenced May 13, 2026
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
2 participants
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
CI-only rollout. Promotes PR #22 from
devtomainso the new.github/workflows/rebuild-on-dispatch-staging.ymllands on the default branch and starts receivingproduct-release-publisheddispatches.Closes the gap surfaced by the bare-SemVer integration test on 2026-05-13: a single dispatch from a product repo now refreshes both production and staging in parallel, eliminating the manual
workflow_dispatchstep needed to verify draft-only fixtures (e.g.pipeline-test-fixture) on staging.Changes since main
f5c466bfeat(ci): staging counterpart of rebuild-on-dispatch.yml (feat(ci): staging counterpart of rebuild-on-dispatch.yml #22)Stats: 1 new file / +58 in
.github/workflows/rebuild-on-dispatch-staging.yml.Routing requirement
repository_dispatchworkflows only fire from files on the repo's default branch (main). Until this PR lands, the new workflow is dormant — dispatches from product repos continue to refresh production only. Merging here flips it active.Staging verification
9b5d3cb(PR feat(ci): staging counterpart of rebuild-on-dispatch.yml #22 merge, 2026-05-13)repository_dispatch. End-to-end exercise comes in the test plan below.Post-merge production smoke checks
deploy-production.ymlflow)Test plan — fires after merge
Cut
0.0.3onblackbrowed-labs/pipeline-test-fixture(GitHub UI):## [0.0.3] — 2026-05-13section toCHANGELOG.md0.0.3, targetmain, title0.0.3, body = the new changelog sectionpipeline-test-fixture'srelease.yml(already updated for0.0.2)Expected:
rebuild-on-dispatch(prod) +rebuild-on-dispatch-staging(this rollout), both greenhttps://dev.blackbrowedlabs.com/produkte/pipeline-test-fixture/version-chip flips to0.0.3without any manualworkflow_dispatchondeploy-staging.ymlhttps://blackbrowedlabs.com/produkte/pipeline-test-fixture/remains 404 (draft:true on the .md) — confirms the staging workflow ran without leaking drafts to prod🤖 Generated with Claude Code