This repository was archived by the owner on Oct 28, 2026. It is now read-only.
Repository navigation
fix: keep deployment HTML and app assets consistent - #336
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Cached entry HTML could reference removed app files during a deployment, leaving the app unable to start. Serve documents through the version-bound Worker asset binding with browser/CDN no-store, and return secured real 404s for absent code files. Fingerprinted assets keep their immutable asset-first delivery.
The loader can recover from confirmed missing old assets after finding a matching newer same-origin Wasm/JavaScript pair. Recovery is bounded to one navigation, preserves the route, and retains the manual Reload control. A successful boot adds no recovery request.
Validation: 709 native tests and the required formatting, native/Wasm Clippy and license checks; 31 focused recovery/cache cases; full local suites with 837 functional, 70 smoothness and 18 static passes, plus the existing declared skips. Exact-source audit preserves all 959 prior case identities and adds 23 active regressions. Existing performance limits, test oracles and Actions triggers are unchanged.
Each full document load adds one Worker invocation and one static-binding read. Client-side navigation retains its existing cost; BUDGET.md documents the Free-plan capacity impact.