Repository navigation
chore(deps): pin MoonUI to the binary download error check - #951
Merged
Merged
Conversation
Moves the MoonUI pin to edef41c9, which makes raw binary downloads reject HTTP error responses instead of saving the error body (#115). The release builds from the pinned revision, so the pin has to match the MoonUI master that CI already tested.
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.
What & why
Re-pins MoonUI from 697851c4 to edef41c9 (Moonbot-Tech/MoonUI#115: raw binary downloads reject HTTP error responses). Needed before the next release: the release builds from the pinned revision.
How to verify
cargo fetch --lockedexits 0;cargo check -p moon-ui-gpuiis green locally.