deps: bump uvicorn from 0.51.0 to 0.52.0

[dependabot]

Bumps uvicorn from 0.51.0 to 0.52.0.

Release notes

Sourced from uvicorn's releases.

Version 0.52.0

This release adds an experimental HTTP/1.1 implementation backed by zttp, a sans-IO HTTP parser I've been developing on the side: a core written in Zig, with bindings to Python. It has been running under a fuzzer for some weeks now, and has been through multiple rounds of security auditing.

It is still experimental, so don't put it in front of production traffic yet. Try it with --http zttp, and please send any feedback to the issue tracker.

Added

• Add an experimental zttp HTTP/1.1 implementation, selectable with --http zttp (#2979)

Fixed

• Keep non-ASCII WebSocket request headers intact with websockets 17.0, which encodes them with ISO-8859-1 (#3036)

Full Changelog: Kludex/uvicorn@0.51.0...0.52.0

Changelog

Sourced from uvicorn's changelog.

0.52.0 (July 29, 2026)

This release adds an experimental HTTP/1.1 implementation backed by zttp, a sans-IO HTTP parser I've been developing on the side: a core written in Zig, with bindings to Python. It has been running under a fuzzer for some weeks now, and has been through multiple rounds of security auditing.

It is still experimental, so don't put it in front of production traffic yet. Try it with --http zttp, and please send any feedback to the issue tracker.

Added

• Add an experimental zttp HTTP/1.1 implementation, selectable with --http zttp (#2979)

Fixed

• Keep non-ASCII WebSocket request headers intact with websockets 17.0, which encodes them with ISO-8859-1 (#3036)

Commits

• 8f1b884 Version 0.52.0 (#3044)
• f6833db Add experimental zttp HTTP/1.1 protocol (#2979)
• d26c85c Prepare compatibility with websockets 17.0. (#3036)
• 7e11cc6 Clarify how limit_concurrency and backlog differ (#3029)
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[cdeust]

ZETETIC-REVIEW: APPROVE

uvicorn 0.51.0→0.52.0 (runtime, minor) — reviewed on evidence.

• Scope verified: the diff touches dependency manifests and lockfiles only; zero application source files are modified, so no behaviour change can enter through this PR except via the dependency itself.
• Exercised, not assumed: the full suite ran against the new version on this branch and is green. For a dependency bump that is the load-bearing evidence — the tests are what would surface an incompatible change.
• Blast radius: a version bump's risk lives in the dependency's own behaviour, which the suite covers for the paths this repository uses. Paths it does not use are not a risk this repository carries.

No findings.

[cdeust]

ZETETIC-REVIEW: APPROVE

Reviewed 2026-08-10. Checks green (no failure, only conditional skips), diff read in full: it is a pin bump and nothing else — no source file, no workflow logic, no configuration semantics changed.

Actions are pinned by commit SHA with the version as a trailing comment, which is the form that survives a tag being moved; Python dependencies keep their --hash lines, so the lockfile stays hash-verified. The bump is exercised by the same required suite as any other change, and that suite passed on this head.

No further verification was warranted for a change of this shape, and none is claimed.