Repository navigation
chore: promote image request fix and 0.1.22 to main - #87
Merged
Merged
Conversation
fix: admit image-heavy requests up to 256 MiB
pavelhov
changed the title
pavelhov
marked this pull request as ready for review
October 22, 2026 20:16
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
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.
Promotes the image-heavy request fix and version 0.1.22 to main. Requests between 128 and 256 MiB now reach normal processing because the HTTP listener shares the parser’s existing limit. Includes aaaa358 and e46ed16 from #86.
Validation: #86 CI passed; local typecheck, privacy scan, all 632 proxy test files, GUI lint/i18n/888 tests/build, docs build, macOS core/UI tests, and CLI smoke passed. The listener regression fails without the option and passes with it.
The universal macOS archive is built from e46ed16, with its fixed runtime files matched to source. Its checksum, signed feed, and all 17 referenced archives verify. Fresh arm64 installed updater tests passed for stopped, native-routing, proxy-routing, and active-request recovery; Intel slices are verified, but Intel execution is unavailable without Rosetta.
Security and distribution review: no authentication, credential, logging, updater, or publishing-tool changes. The existing external single-link 0600 key matches the public key, and Sparkle 2.9.6 tools match pinned hashes. The release remains an unnotarized preview. Downloaded draft assets must verify before publication, and the public latest feed must verify afterward.