feat(ci): staging counterpart of rebuild-on-dispatch.yml#22
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>
2 tasks
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.
Summary
Adds a staging-side mirror of
rebuild-on-dispatch.yml. A singleproduct-release-publisheddispatch from a product repo now refreshes both production and staging in parallel.Closes the gap surfaced by the bare-SemVer integration test on 2026-05-13: staging was not refreshed by product-release dispatches, so verifying a new release on a draft-only product (e.g.
pipeline-test-fixture) required a manualworkflow_dispatchondeploy-staging.yml.Changes
.github/workflows/rebuild-on-dispatch-staging.yml(new, 58 lines)repository_dispatch→product-release-published)devinstead ofmainPUBLIC_ENVIRONMENT: staging,command: deploy --env stagingConvention match
Mirrors the per-environment-file pattern already in place across two other pairs:
deploy-production.ymldeploy-staging.ymlrebuild-nightly.ymlrebuild-nightly-staging.ymlrebuild-on-dispatch.ymlrebuild-on-dispatch-staging.yml(this PR)Routing note
repository_dispatchworkflows only fire from files on the repo's default branch (main). So this file becomes active only after the nextdev → mainrollout. The header comment in the new file captures this for future readers.Test plan
After this PR merges to
devand the subsequentdev → mainrollout lands, cut a0.0.3release onpipeline-test-fixture(UI). Expected: the dispatch fires both workflows on this repo in parallel, both complete green, and staging picks up0.0.3without any manualworkflow_dispatch.devpush — file only fires on dispatch from default branch)devdev → mainrollout PRmain0.0.3onpipeline-test-fixturevia GitHub UI (CHANGELOG section + release)rebuild-on-dispatch(production) ANDrebuild-on-dispatch-staging(this PR), both greendev.blackbrowedlabs.com/produkte/pipeline-test-fixture/version-chip shows0.0.3without a manual staging deploy/produkte/pipeline-test-fixture/remains 404 —draft: trueon the .md file)🤖 Generated with Claude Code