Skip to content

ci(deploy): deploy the US and EU instances in parallel - #1962

Merged
Makisuo merged 1 commit into
mainfrom
ci/deploy-eu-parallel
Oct 30, 2026
Merged

ci(deploy): deploy the US and EU instances in parallel#1962
Makisuo merged 1 commit into
mainfrom
ci/deploy-eu-parallel

ci(deploy): deploy the US and EU instances in parallel

62392d6
Select commit
Loading
Failed to load commit list.
Maple Review Bot / Maple / review succeeded Oct 30, 2026 in 47s

Confidence 10/10 · No issues found

🟢 Confidence 10/10 · safe to merge
Two-line workflow change; parallel instances share no state — distinct stage, DB and account-wide resources owned by us only. Loss of the US canary is intentional and stated.
no findings · tests not needed · risk medium

deploy-prd-eu now waits only on ingest-binary, so both production instances deploy at the same time. The instances share no mutable resource, so the change is safe to merge; it trades the US-as-canary sequencing for half the deploy time.

  • deploy-prd-eu needs only ingest-binary, dropping its dependency on deploy-prd
What was checked
  • Instances are isolated: MAPLE_STAGE prd/prd-eu (deploy-prd-instance.yml:28) and resolvePlanetscaleDatabase returns maple vs maple-eu (stage.ts:232)
  • No shared deploy resource: profile.deploys.sharedApps is false for prd-eu (profile.test.ts:22), and account-wide Workers Observability destinations are owned only by us (observability.ts:17)
  • deployment-gate still needs both jobs with always() (deploy-prd.yml:53), so a skipped or failed US deploy still fails the run

62392d6 · Updated on every push. Reply "won't fix" to dismiss a finding, or mention @maple-review-bot to ask about one.

View more details on Maple Review Bot