Skip to content

Fix deploy to consume Nearby Universe from R2 - #430

Merged
alowpoly merged 6 commits into
mainfrom
fix/deploy-consume-nearby-r2
Sep 20, 2026
Merged

alowpoly merged 6 commits into
mainfrom
fix/deploy-consume-nearby-r2

Conversation

@alowpoly

Copy link
Copy Markdown
Contributor

What changed

  • stop regenerating Nearby Universe during deploy
  • resolve its prepared point and cloud resources from the committed content-addressed R2 inventories
  • exercise the production asset-origin build and metadata drift guard in PR CI
  • accept valid @2x filenames in the deploy asset-closure verifier

Why

Automatic deploy run 35510300326 failed because build:deploy rewrote committed nearby-universe metadata after PR #426 merged. The payload is already published to R2; deploy should consume that package, not regenerate it.

Validation

  • clean production-origin build:deploy completed (995 pages)
  • check:deploy-assets verified 3,911 emitted R2 URLs across 1,529 deploy files
  • built bundle contains the inventoried nearby-universe points.json and cloud.webp URLs while no local payload was present
  • focused Node tests: 18 passed
  • typecheck:tools
  • typecheck:shell
  • git diff --check

@alowpoly
alowpoly merged commit 0fb1c2b into main Sep 20, 2026
12 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant