Fix cold deploy from R2 without rebaking assets - #426
Merged
Merged
Conversation
Fix deploy generation of source catalogues
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.
Fixes the cold deployment path without rebaking prepared packages or bulk-restoring the R2 corpus.
What changed
build:deployprepared/presentation.jsonandprepared/provenance.jsonfor catalogue compilation; large dataset textures remain on R2pnpm build:deploypath on relevant pull requestsWhy
The previous deploy path mixed source authoring, installed package metadata, and local-file assumptions. That caused successive cold-checkout failures for ignored catalogues, source-only contexts, and M31/M33 metadata. Restoring every inventoried asset would hide those boundaries and can download the full corpus, so this keeps the deploy input narrow and content-addressed.
This PR now consolidates and supersedes the incremental work from #427, #428, and #429 while retaining the original #426 history.
Validation
pnpm build:deploypasses on commit44c827f53aNo assets are generated or published by this PR.