chore: update minifront bundled assets #5090
Merged
Conversation
This file contains 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
Built from head on web repo 28e2ccb6a8255f793866e5f59d8d334ab32510ad. Tested locally, and I see the new version displayed in my local browser, in the footer.
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.
Describe your changes
Built from head on web repo 28e2ccb6a8255f793866e5f59d8d334ab32510ad. Tested locally, and I see the new version displayed in my local browser, in the footer.
Issue ticket number and link
Closes #4965.
Testing and review
If you have the patience, pull down this branch and use a local node with prax. On the frontend page, you should see:
Which maps to this commit: penumbra-zone/web@28e2ccb and notably includes the skip widget fix immediately preceding it, in penumbra-zone/web@03597b7
Checklist before requesting a review
I have added guiding text to explain how a reviewer should test these changes.
If this code contains consensus-breaking changes, I have added the "consensus-breaking" label. Otherwise, I declare my belief that there are not consensus-breaking changes, for the following reason: