chore: update minifront bundled assets #5119
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
3 tasks
|
@TalDerei mentioned a possible additional commit that'd be nice to include, so pausing for a bit. |
Built from head on web repo 68a1cd50391197ee180af9966e474e04363c50f8 Tested locally, and I see the new version displayed in my local browser, in the footer.
conorsch
force-pushed
the
ci-bump-bundled-minifront-2025-03-05
branch
from
82f54fd to
32f17cc
Compare
|
Updated the bundled commit hash (from the web repo) from fb5dcb6e7d37facc3fb07e800e8dadc064c40cb9 to 68a1cd50391197ee180af9966e474e04363c50f8, to include penumbra-zone/web#2095. |
1 task
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 68a1cd50391197ee180af9966e474e04363c50f8. Tested locally, and I see the new version displayed in my local browser, in the footer.
Issue ticket number and link
No specific issue, updating opportunistically. Towards #5118.
Testing and review
We don't have automated tests to ensure the version spec, so I already confirmed locally that the appropriate commit has is referenced. Therefore, as long as CI is green on this PR, we're good to go.
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: