Repository navigation
chore: exclude multidict 7.2.0, which breaks Litestar headers - #13
Merged
Merged
Conversation
This was referenced Oct 24, 2026
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.
multidict 7.2.0 made
CIMultiDictProxy.__new__()require the proxied multidict. Litestar'sHeaderssubclass takes the raw ASGI header list and converts it in__init__, so on 7.2.0 every Litestar request fails with a TypeError while reading headers. That is what broke the 9 tests intests/test_litestar.pyin the scheduled dependency check.This adds
multidict!=7.2.0to[tool.uv] constraint-dependencies. The constraint applies to this repo's lock and CI only, and the published package metadata stays the same. Because it excludes one version, a fixed release will resolve without another change here.I checked the versions locally. The Litestar tests pass with multidict 7.0.0 on litestar 2.24.0 and 2.25.0, and with 7.1.0 on 2.25.0. They fail with 7.2.0 on both litestar versions. With the constraint,
just lint-ciandjust test-cipass (89 tests, 100% coverage). The floors job steps resolve multidict 7.1.0 and pass on litestar 2.19.0.Remove the constraint once a multidict release fixes aio-libs/multidict#1824.
Closes #11