Repository navigation
Fix Ripple transparency page deployment package - #27
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
1 participant
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 footer-linked /ripple/updates page returned 404 because the Worker build omitted its generated HTML. Include that asset and verify the real built Worker serves both transparency URL forms.
Validation: full Node tests, ordered content-generation checks, production build and hosted route/snapshot readback. Browser rendering and native exports remain separately unperformed; this patch leaves the report implementation unchanged. The audit retains the initial packaging failure and the actual private assessment/research readback results.