Repository navigation
Preserve excluded WASM files during Pages deployment - #145
Merged
Merged
Conversation
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.
The Pages deployment workflow currently removes the R2-hosted WASM directory with a command prohibited by the owner’s workspace instructions. Move it into the job’s temporary directory instead, preserving the build bytes while excluding them from the Pages upload.
Validated with a temporary build fixture: the Pages shell remains in
dist, the WASM directory is excluded, and its bytes remain intact in the temporary destination.git diff --checkpasses. No application, authentication, database, or production configuration changes.Release preparation for #141; this PR does not establish real-account acceptance or deploy production.