chore(docs): document staging dispatch workflow in TECH_STACK §7#24
Merged
Conversation
Updates §7 step 3 to reflect the actual deployed state after #23: a `product-release-published` dispatch now fires both `rebuild-on-dispatch.yml` (production) and `rebuild-on-dispatch-staging.yml` (staging) in parallel. Adjusts step 4 to clarify that the ~60-seconds-to-appear claim covers both environments. Co-Authored-By: Claude <noreply@anthropic.com>
1 task
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
Updates
docs/TECH_STACK.md§7 step 3 to reflect the deployed state after #23: aproduct-release-publisheddispatch now fires bothrebuild-on-dispatch.yml(production) andrebuild-on-dispatch-staging.yml(staging) in parallel.Step 4 is also touched so the ~60-seconds-to-appear claim explicitly covers both environments.
Diff
Single file / +2 / −2 in
docs/TECH_STACK.md. No other surfaces touched.Out of scope — surfaced for backlog
Two other parts of TECH_STACK are stale, but not from today's work:
rebuild-nightly.yml; therebuild-nightly-staging.ymlsibling (added under G D.11.2 per BOOTSTRAP) isn't named. Also incorrectly says the fallback is a "Cron Trigger in the production Worker" — it's GH Actions Cron.deploy.yml + rebuild-on-dispatch.yml. Out of date:deploy.ymlwas split intodeploy-production.yml+deploy-staging.yml, andci-pr.yml,rebuild-nightly.yml,rebuild-nightly-staging.yml,rebuild-on-dispatch-staging.yml,verify-cloudflare-facts.ymlare all missing.Not touched here per the no-mid-flight-retrofit rule — both are dedicated backlog items if you want them.
🤖 Generated with Claude Code