[dependabot]

Bumps the python-runtime group with 19 updates in the / directory:

Package	From	To
asyncssh	2.24.0	2.24.1
fastapi	0.139.0	0.162.0
httpx2	2.12.0	2.16.0
pydantic	2.13.4	2.14.2
pydantic-settings	2.14.2	2.16.2
sqlalchemy	2.0.51	2.1.6
uvicorn	0.51.0	0.54.0
uuid-utils	0.17.0	1.2.0
alembic	1.18.5	1.20.1
dbos	3.2.0	3.4.0
redis	8.0.1	8.1.0
tomlkit	0.15.1	0.15.2
cryptography	49.0.0	50.0.2
fastmcp	4.1.0	4.1.6
jsonpointer	3.1.1	3.8
authlib	1.7.2	1.9.3
joserfc	1.7.4	1.8.0
slack-sdk	3.44.1	3.46.0
aiohttp	3.14.3	3.14.5

Updates asyncssh from 2.24.0 to 2.24.1

Changelog

Sourced from asyncssh's changelog.

Release 2.24.1 (3 Oct 2026)

• Fixed a potential "short read/write" issue in SFTP, potentially requiring multiple calls to successfully read or write all the data an application requests. Thanks go to Landon Peng for reporting this issue.

• Added protection against unreasonable packet lengths when parsing SSH and SFTP packets, avoiding a potential denial of service attack. Thanks go to zhangph (GitHub user afldl) for suggesting this change.

• Added restrictions on which SSH channel requests are allowed to be sent more than once on a channel. Thanks go to zhangph (GitHub user afldl) for reporting this issue for shell/exec/subsystem requests.

• Improved error reporting of a client trying to set multiple attributes on a file, when some of the operations aren't supported. Thanks go to Kevin O'Neil for reporting this issue and helping to test this fix.

• Improved path sanitizaation for SCP, to protect against additional "path traversal" attacks. Thanks go to GitHub user jankesec for reporting the issue and providing a proposed fix.

• Fixed a race condition in server authentication that could result in the wrong username being set as the authenticated user. Thanks go to OpenAI security team for reporting this issue and providing a suggested fix.

• Fixed a possible leak of options across authentication attempts when multiple authentication requests are attempted on a connection. Thanks go to GitHub user 0xW41th for reporting this issue and providing a suggested fix.

• Fixed multiple SFTP "path traversal" issues, where a malicious SFTP server could trick an SFTP client into writing outside of the requested target directory. Thanks go to Youjoon Yoon, Khizar Ali Shah, and GitHub user L1nq0 for reporting these issues and suggesting possible fixes.

• Fixed multiple SFTP chroot escape issues, where a client could read and write files outside of a chroot'd AsyncSSH SFTP server. Thanks go to GitHub user LorenzMap, Arpit Jain, and Mario Madersbacher for reporting these issues and suggesting possible fixes.

• Fixed revocation checking to handle the case where a host certificate is sent with a trusted CA but where the host key within the certificate is marked as revoked. Thanks go to Mohammad Thabet Hassan for reporting this issue.

... (truncated)

Commits

• 5dbdf18 Bump version number up to 2.24.1 and update change log
• 1c3212d Disallow empty username substitutions in config file token expansion
• 307f093 Fix flow control issue on SSH channels
• 6cd3357 Fix revocation check on certs signed by a trusted CA
• ec34b9d Update pylint module size limit
• 382ee2c Improve SCP path sanitization
• 47cd8f4 Fix typing issue
• 9331e97 Enhance fix for download directory escape in SFTP client
• aee6203 Enhance protection against zero packet size in dropbear case
• 742f091 More GSSAPI unit test improvements
• Additional commits viewable in compare view

Updates fastapi from 0.139.0 to 0.162.0

Release notes

Sourced from fastapi's releases.

0.162.0

Omitted bool and bool | None form fields now use their declared defaults or produce missing-field errors, consistent with other fields and Pydantic behavior. FastAPI no longer infers False for omitted booleans. This applies to individual form parameters, form models, and unions of form models.

Omitted boolean model fields are excluded from model_dump(exclude_unset=True), and their defaults no longer count as submitted fields during union selection. Default factories and validate_default follow the usual rules.

For HTML checkboxes, declare a boolean with a default of False. See Boolean Form Fields.

Breaking Changes

• 🐛 Restore default handling for omitted boolean form fields. PR #16605 by @​tiangolo.

0.161.1

Fixes

• 🐛 Fix OpenAPI schemas for standalone nullable form unions. PR #16598 by @​tiangolo.

0.161.0

Features

• ✨ Add support for combining unions of form models. PR #16596 by @​tiangolo.

0.160.0

Query, header, cookie, and form parameter models now apply their extra configuration to all submitted fields in the same parameter location, consistent with Pydantic behavior. This includes fields declared in other models, individual parameters, or dependencies, which were previously excluded.

With extra="forbid", fields outside the model are rejected even if another parameter declares them. With extra="allow", those fields are included as model extras. With the default extra="ignore", they are ignored.

Breaking Changes

• 🐛 Apply each parameter model's extra configuration to sibling fields. PR #16594 by @​tiangolo.

Internal

• ⬆ Bump certifi from 2026.1.4 to 2026.10.19. PR #16571 by @​dependabot[bot].

0.159.1

Features

• ✨ Add support for optional unions of form models. PR #16586 by @​tiangolo.

0.159.0

Features

• ✨ Add support for optional query, header, and cookie parameter models. PR #16584 by @​tiangolo.

0.158.2

Features

• ✨ Add support for optional form models. PR #16582 by @​tiangolo.

0.158.1

... (truncated)

Commits

• 7a0a3f0 🔖 Release version 0.162.0 (#16606)
• b56f7c6 📝 Update release notes
• f02ef49 🐛 Restore default handling for omitted boolean form fields (#16605)
• 69ddc2b 🔖 Release version 0.161.1 (#16599)
• 0cafa07 📝 Update release notes
• f90d036 🐛 Fix OpenAPI schemas for standalone nullable form unions (#16598)
• 80c8742 🔖 Release version 0.161.0 (#16597)
• b105209 📝 Update release notes
• e42ac0a ✨ Add support for combining unions of form models (#16596)
• addd077 🔖 Release version 0.160.0 (#16595)
• Additional commits viewable in compare view

Updates httpx2 from 2.12.0 to 2.16.0

Release notes

Sourced from httpx2's releases.

v2.16.0

Highlights

🍪 Faster requests with large cookie jars

Building the Cookie header no longer scans every cookie in the jar. The client reuses its jar instead of copying it on every request and redirect (#1284), only looks up the domains that can match the request host, and skips the expired cookie sweep until a cookie is due (#1285). With 1,000 cookies across 500 domains, building the Cookie header is about 18 times faster.

Cookies from different domains are now sent from the least to the most specific domain, for example .example.org before sub.example.org, instead of in the order the domains were added. Cookies with longer paths still come first.

httpx2

Changed

• Look up only the cookie domains that match the request host, and skip the expired cookie sweep until a cookie is due. With 1,000 cookies across 500 domains, building the Cookie header is about 18 times faster. Cookies from different domains are now sent from the least to the most specific domain (#1285).

Fixed

• Reuse the client cookie jar instead of copying it on every request and redirect. A custom policy set with client.cookies.jar.set_policy() now applies to outgoing requests (#1284).

httpcore2

No changes since 2.15.1. Version bumped to stay in lockstep with httpx2.

Full Changelog: pydantic/httpx2@v2.15.1...v2.16.0

v2.15.1

Highlights

🔒 Flat CPU usage for long-lived clients on Linux

On Linux, the default SSL context is now configured once instead of on every handshake (#1253). With OpenSSL older than 3.4, each handshake added a duplicate certificate lookup path, so CPU usage per request grew over the lifetime of a reused client. Certificate verification is unchanged, and Windows and macOS still use truststore.

httpx2

Fixed

• Configure the default SSL context once on Linux, instead of on every handshake. With OpenSSL older than 3.4, CPU usage grew over the lifetime of a reused client (#1253).

httpcore2

Fixed

• Configure the default SSL context once on Linux, instead of on every handshake. With OpenSSL older than 3.4, CPU usage grew over the lifetime of a reused client (#1253).

Full Changelog: pydantic/httpx2@v2.15.0...v2.15.1

v2.15.0

Highlights

🐍 Python 3.11+ required

... (truncated)

Changelog

Sourced from httpx2's changelog.

2.16.0 (October 21st, 2026)

Changed

• Look up only the cookie domains that match the request host, and skip the expired cookie sweep until a cookie is due. With 1,000 cookies across 500 domains, building the Cookie header is about 18 times faster. Cookies from different domains are now sent from the least to the most specific domain. (#1285)

Fixed

• Reuse the client cookie jar instead of copying it on every request and redirect. A custom policy set with client.cookies.jar.set_policy() now applies to outgoing requests. (#1284)

2.15.1 (October 19th, 2026)

Fixed

• Configure the default SSL context once on Linux, instead of on every handshake. With OpenSSL older than 3.4, CPU usage grew over the lifetime of a reused client. (#1253)

2.15.0 (October 19th, 2026)

Removed

• Drop support for Python 3.10. (#1274)

2.14.0 (October 18th, 2026)

Added

• Match IP CIDR ranges, like 192.168.0.0/16 and [fe80::]/10, in NO_PROXY and mounts. Requests to any address in the range now bypass the proxy; previously only the network address itself did. (#1165)
• Accept bracketed IPv6 addresses, like [::1] and [::1]:8080, in NO_PROXY. (#1267)

Changed

• Raise InvalidURL for a mounts key with an IP host followed by anything other than a valid CIDR prefix, like all://10.0.0.0/33. (#1165)

Fixed

• Ignore NO_PROXY entries that cannot be parsed, instead of raising InvalidURL when the client is created. (#1267)
• Import httpx2 on FIPS-enforced Python builds without hashlib.md5. DigestAuth raises ProtocolError when the server asks for an unavailable algorithm. (#1130)
• Handle reads after an ASGI WebSocket app shuts down, instead of leaking anyio exceptions. (#1233)
• Stop the sync WebSocket session from hanging on exit when its event queue is full. (#1123)

... (truncated)

Commits

• 6bfbf29 Prepare version 2.16.0 (#1286)
• a1e461e Look up only matching cookie domains when building the Cookie header (#1285)
• fc6ff89 Reuse the client cookie jar instead of copying it per request (#1284)
• 6dd59b9 Prepare version 2.15.1 (#1279)
• 7715bf0 Configure the default Linux SSL context once instead of per handshake (#1253)
• 6078596 Prepare version 2.15.0 (#1278)
• 5b26c25 Drop support for Python 3.10 (#1274)
• 4fa853a Prepare version 2.14.0 (#1271)
• dd7701a Support IP CIDR ranges in NO_PROXY (#1165)
• cd50836 Accept bracketed IPv6 and skip unparseable entries in NO_PROXY (#1267)
• Additional commits viewable in compare view

Updates pydantic from 2.13.4 to 2.14.2

Release notes

Sourced from pydantic's releases.

v2.14.2 2026-10-29

v2.14.2 (2026-10-29)

This release addresses 2 security issues, GHSA-qpmf-fgh3-ff25 and GHSA-3r8g-cqwr-jr29.

Packaging

• Bump PyO3 to 0.30.1, jiter to 0.18.0, use PyFrozenDict by @​Viicos in #14003
• Bump speedate to v0.18.0 by @​Viicos in #14007
• Publish pydantic-core wheels for PyPy 8.0 (pp80 ABI) by @​Viicos in #14083

Performance

• Avoid Python tuple allocation during model fields validation by @​Viicos in #13955
• Lazily call repr of values during nested union serialization by @​Viicos in #14082
• Skip decorator field checks when no field decorators exist by @​alexmojaki in #14111
• Avoid heap allocation for small JSON model field buffers by @​alexmojaki in #14113

Fixes

• Make JSON validation by iteration consistent with Python approach by @​davidhewitt in #13275.

  JSON validation now handles field lookup and extra data the same way as Python validation. In particular, keys that only match an unused alias or field name are now treated as extra data, instead of being silently dropped:

  from pydantic import BaseModel, ConfigDict
  from pydantic.alias_generators import to_camel
  class Page(BaseModel):
  model_config = ConfigDict(extra='forbid', alias_generator=to_camel)
  page_size: int = 10
  
  Page.model_validate_json('{"page_size": 50}')
  Before: Page(page_size=10)
  After: ValidationError (extra_forbidden)

  See the pull request for the full list of behavior changes. This change addresses GHSA-qpmf-fgh3-ff25.

• Ignore extra data matching a field name in TypedDict and dataclasses with extra=allow by @​Viicos in #14090. Addresses GHSA-3r8g-cqwr-jr29.

• Fix unpickling of generic classes defined in separate module by @​Viicos in #13994

• Support explicit by_alias overriding validate_by_alias in validation JSON schemas by @​Viicos in #13997

• Fix mypy plugin crash on deferred empty model by @​ilevkivskyi in #14027

• Fix infinite recursion when validating an invalid default with PydanticUseDefault by @​Viicos in #14028

• Implement recursion guard for validate_strings() by @​Viicos in #14029

... (truncated)

Changelog

Sourced from pydantic's changelog.

v2.14.2 (2026-10-29)

GitHub release

What's Changed

Packaging

• Bump PyO3 to 0.30.1, jiter to 0.18.0, use PyFrozenDict by @​Viicos in #14003
• Bump speedate to v0.18.0 by @​Viicos in #14007
• Publish pydantic-core wheels for PyPy 8.0 (pp80 ABI) by @​Viicos in #14083

Performance

• Avoid Python tuple allocation during model fields validation by @​Viicos in #13955
• Lazily call repr of values during nested union serialization by @​Viicos in #14082
• Skip decorator field checks when no field decorators exist by @​alexmojaki in #14111
• Avoid heap allocation for small JSON model field buffers by @​alexmojaki in #14113

Fixes

• Make JSON validation by iteration consistent with Python approach by @​davidhewitt in #13275.

  JSON validation now handles field lookup and extra data the same way as Python validation. In particular, keys that only match an unused alias or field name are now treated as extra data, instead of being silently dropped:

  from pydantic import BaseModel, ConfigDict
  from pydantic.alias_generators import to_camel
  class Page(BaseModel):
  model_config = ConfigDict(extra='forbid', alias_generator=to_camel)
  page_size: int = 10
  
  Page.model_validate_json('{"page_size": 50}')
  Before: Page(page_size=10)
  After: ValidationError (extra_forbidden)

  See the pull request for the full list of behavior changes.

• Fix unpickling of generic classes defined in separate module by @​Viicos in #13994

• Support explicit by_alias overriding validate_by_alias in validation JSON schemas by @​Viicos in #13997

• Fix mypy plugin crash on deferred empty model by @​ilevkivskyi in #14027

• Fix infinite recursion when validating an invalid default with PydanticUseDefault by @​Viicos in #14028

• Implement recursion guard for validate_strings() by @​Viicos in #14029

• Support named tuples in Sequence serialization by @​Viicos in #14033

... (truncated)

Commits

• aa540ac Update changelog for v2.14.2
• 6cde12f Update changelog for v2.14.2
• 2db7c25 Fix deep copy of self-referential models
• d783154 Update changelog for v2.14.2
• df49b6c Avoid heap allocation for small JSON model field buffers
• cd93e69 Skip decorator field checks when no field decorators exist
• 2771e57 Make JSON validation by iteration consistent with Python approach
• 8102e3f Avoid Python tuple allocation during model fields validation
• dd139b5 Bump pydantic.v1 namespace to v1.10.27
• 66155f9 Prepare release v2.14.2
• Additional commits viewable in compare view

Updates pydantic-settings from 2.14.2 to 2.16.2

Release notes

Sourced from pydantic-settings's releases.

v2.16.2

Highlights

This patch release fixes env decoding of nested dictionary values, CliApp handling of AliasPath, nested secrets directory precedence and discriminated union defaults with nested_model_default_partial_update.

Behavior changes

• An explicit secrets_dir on NestedSecretsSettingsSource now takes precedence (#1093). Previously it was ignored when the wrapped SecretsSettingsSource inherited a directory from model config, and an explicit empty list was masked too. The order is now: the wrapper's secrets_dir argument, then the wrapped source's directory, then model config. If you pass both Settings(_secrets_dir=...) and NestedSecretsSettingsSource(..., secrets_dir=...), the wrapper's argument now wins.

Bug fixes

Env and dotenv sources

• Dictionary values typed as a union, such as dict[str, list[str] | str] or dict[str, list[str] | None], now JSON-decode values set through env_nested_delimiter (#1089, #1097). Only JSON arrays and objects are decoded, so plain values like 123, true or "quoted" are kept as strings. Decoding follows enable_decoding and the NoDecode/ForceDecode of the field that holds the dict, and type aliases and Annotated value types are resolved.
• Nested dictionary values such as dict[str, list[dict[str, str]]] are decoded at the right level again (#1109), so APP_VALUES__X='[{"k":"v"}]' no longer reaches validation as a string.

CLI

• CliApp.run now rebuilds AliasPath inputs for BaseModel and pydantic dataclass commands (#1096). A supplied path used to be reduced to the field name, which failed validation. AliasChoices priority is respected and unsupplied path defaults are left to the model.

Discriminated union defaults

• With nested_model_default_partial_update=True, inner discriminated unions written as Annotated[..., Field(discriminator='...')] are now detected (#1076). When the incoming tag selects another member, the default's fields are no longer merged into it.
• A stdlib dataclass default on a discriminated union field no longer raises NameError when another field of the dataclass has a string annotation naming a local class (#1077). Only the discriminator's own annotation is resolved now.

What's Changed

• build(deps): bump the python-packages group with 3 updates by @​dependabot[bot] in pydantic/pydantic-settings#1056
• Detect nested Field discriminators in default partial updates by @​digit50 in pydantic/pydantic-settings#1076
• Resolve only the discriminator annotation of stdlib dataclass defaults by @​digit50 in pydantic/pydantic-settings#1077
• Decode nested dictionary values with complex union types by @​chering14 in pydantic/pydantic-settings#1089
• Fix regressions from nested dict union value decoding (#1089) by @​hramezani in pydantic/pydantic-settings#1097
• Fix explicit nested secrets directory precedence by @​DivyamTalwar in pydantic/pydantic-settings#1093
• Fix CliApp reconstruction of AliasPath inputs by @​DivyamTalwar in pydantic/pydantic-settings#1096
• Fix JSON decoding of nested dictionary environment values by @​Hugohong258 in pydantic/pydantic-settings#1109
• Prepare release 2.16.2 by @​hramezani in pydantic/pydantic-settings#1111

New Contributors

• @​digit50 made their first contribution in pydantic/pydantic-settings#1076
• @​chering14 made their first contribution in pydantic/pydantic-settings#1089
• @​DivyamTalwar made their first contribution in pydantic/pydantic-settings#1093
• @​Hugohong258 made their first contribution in pydantic/pydantic-settings#1109

Full Changelog: pydantic/pydantic-settings@v2.16.1...v2.16.2

v2.16.1

Highlights

... (truncated)

Commits

• 94150a0 Prepare release 2.16.2 (#1111)
• 9e02de0 Fix JSON decoding of nested dictionary environment values (#1109)
• 7e2dacb Fix CliApp reconstruction of AliasPath inputs (#1096)
• 2d1f924 Fix explicit nested secrets directory precedence (#1093)
• e9588ae Fix regressions from nested dict union value decoding (#1089) (#1097)
• e71a53e Decode nested dictionary values with complex union types (#1089)
• 8dc9e05 Resolve only the discriminator annotation of stdlib dataclass defaults (#1077)
• c50c853 Detect nested Field discriminators in default partial updates (#1076)
• 9aabb8a build(deps): bump the python-packages group with 3 updates (#1056)
• 4e286e2 Prepare release 2.16.1 (#1087)
• Additional commits viewable in compare view

Updates sqlalchemy from 2.0.51 to 2.1.6

Release notes

Sourced from sqlalchemy's releases.

2.1.6

Released: October 21, 2026

orm

• [orm] [bug] Fixed issue where a Session flush that replaced an expired object in the identity map with a newly flushed object of the same primary key would emit a SELECT to refresh the expired object, solely in order to determine whether to emit an "Identity map already had an identity" warning. This could occur when a row loaded within a transaction is rolled back and its primary key value is subsequently reused, and could lead to an AttributeError if the expired object were garbage collected during that load. The check now emits no SQL, and an expired object that is replaced in this way no longer causes the warning to be emitted.

  This change is also backported to: 2.0.56

  References: #13711

• [orm] [bug] [regression] Fixed regression caused by #13070 where using more than one orm.with_loader_criteria() option for the same entity, where the criteria made use of correlated subqueries referring to that entity, would fail with a RecursionError when compiling.

  References: #13701

• [orm] [bug] [regression] Fixed regression caused by the new implementation of .params() for statements introduced in #7066, where parameter values passed to the .params() method of an ORM statement created using Select.from_statement() would not be applied when the statement was compiled without the compiled statement cache, such as when the cache was disabled or when the statement was stringified directly, leading to an error that a value is required for the bound parameter.

  References: #13709

orm extensions

• [bug] [orm extensions] Fixed an issue in the instrumentation_toplevel extension where unrelated classes inheriting from typing.Generic could incorrectly raise a TypeError when using different instrumentation implementations. Pull request courtesy TomasCaruso10.

  This change is also backported to: 2.0.56

  References: #13680

... (truncated)

Commits

• See full diff in compare view

Updates uvicorn from 0.51.0 to 0.54.0

Release notes

Sourced from uvicorn's releases.

Version 0.54.0

📨 Send metadata after the response body

uvicorn 0.54.0 adds response trailers and 103 Early Hints to its experimental HTTP/2 implementation through zttp.

uv add uvicorn==0.54.0 "zttp>=0.0.34"

• Send HTTP/2 response trailers (#3146). The ASGI http.response.trailers extension lets applications send metadata, such as checksums, after the response body. Clients must send TE: trailers to receive them. Multiple trailer messages are combined before completing the response.
• HTTP/2 remains experimental and opt-in. Enable it with --http zttp --http2. Upgrade-based h2c and WebSockets over HTTP/2 remain unsupported.

💡 Hint at resources before the final response

• Send 103 Early Hints over HTTP/2 (#3137). Applications can use the ASGI http.response.early_hint extension to send resource hints before the final response. Each supplied link becomes a separate Link header.

Full changelog: 0.53.0...0.54.0

Version 0.53.0

🌐 Opt-in HTTP/2 support

uvicorn 0.53.0 adds experimental HTTP/2 through zttp, alongside a new zuvloop integration and connection-handling improvements.

uv add uvicorn==0.53.0

• Serve HTTP/1.1 and HTTP/2 with zttp (#2982, #3101). Install zttp, then enable HTTP/2 with --http zttp --http2. Uvicorn negotiates HTTP/2 over TLS with ALPN and supports cleartext prior knowledge.
• HTTP/2 remains experimental. Upgrade-based h2c and WebSockets over HTTP/2 are not supported.

⚙️ More event loop choice

• Run Uvicorn with zuvloop (#3104). Install zuvloop separately and select it explicitly with --loop zuvloop on CPython 3.14 or newer.

🛡️ More reliable connections and proxies

• Honor Connection: close token lists (#3103). Uvicorn now parses comma-separated tokens case-insensitively across HTTP implementations.
• Trust IPv6 loopback proxies by default (#3119). The default FORWARDED_ALLOW_IPS value now includes ::1.
• Keep upgraded WebSockets alive (#3107). Uvicorn cancels the HTTP keep-alive timer when the connection becomes a WebSocket.

Full changelog: 0.52.4...0.53.0

Version 0.52.4

Fixed

• Remove duplicate Date headers from accepted WebSocket handshakes with websockets-sansio (#3078)

Full Changelog: Kludex/uvicorn@0.52.3...0.52.4

Version 0.52.3

... (truncated)

Changelog

Sourced from uvicorn's changelog.

0.54.0 (September 24, 2026)

HTTP/2 support remains experimental. Install zttp>=0.0.34 and enable it with --http zttp --http2.

Added

• Add HTTP/2 response trailers through the ASGI http.response.trailers extension. Clients must send TE: trailers to receive them (#3146)
• Add HTTP/2 103 Early Hints through the ASGI http.response.early_hint extension (#3137)

0.53.0 (September 14, 2026)

This release adds experimental HTTP/2 support through zttp. Enable it with --http zttp --http2. Upgrade-based h2c and WebSockets over HTTP/2 are not supported.

Added

• Add experimental HTTP/2 support through zttp (#2982, #3101)
• Add support for zuvloop (#3104)

Fixed

• Handle comma-separated, case-insensitive Connection: close tokens across HTTP implementations (#3103)
• Trust IPv6 loopback in the default FORWARDED_ALLOW_IPS value (#3119)
• Cancel the HTTP keep-alive timer when upgrading to WebSocket (#3107)

0.52.4 (August 18, 2026)

Fixed

• Remove duplicate Date headers from accepted WebSocket handshakes with websockets-sansio (#3078)

0.52.3 (August 13, 2026)

Changed

• Update zttp to 0.0.24 and use its combined receive path, improving HTTP/1.1 request parsing performance (#3067)

0.52.2 (August 13, 2026)

Fixed

• Update zttp to 0.0.22, fixing bodyless request receives and improving HTTP/1 request parsing performance (#3063)

0.52.1 (August 1, 2026)

Fixed

• Complete the closing handshake on server-initiated WebSocket closes in the websockets-sansio and wsproto implementations, waiting for the client's close reply with a 10 second timeout instead of resetting the connection (#3053)
• Add missing write flow control to the websockets-sansio implementation, preventing data truncation on server-initiated closes with large in-flight payloads (#3048)
• Handle connection loss while a WebSocket write is waiting on backpressure (#3050)

... (truncated)

Commits

• 3eb9a9a Version 0.54.0 (#3161)
• cd7ef6d Remove races from supervisor tests (#3134)
• a56c7cc Support HTTP/2 response trailers (#3146)
• 9bd4404 chore(deps): bump anyio from 4.13.0 to 4.14.2 (#3145)
• 21f39ef Add HTTP/2 Early Hints support (#3137)
• 421708f Version 0.53.0 (#3136)
• f1a1bff Unset the keep-alive timer when upgrading to WebSocket (#3107)
• 63971ed Document HTTP/2 support (#3130)
• 7d1a005 Remove race from multiprocess health check test (#3128)
• 5ac6265 Add ::1 to FORWARDED_ALLOW_IPS (#3119)
• Additional commits viewable in compare view

Updates uuid-utils from 0.17.0 to 1.2.0

Release notes

Sourced from uuid-utils's releases.

1.2.0

What's Changed

• build: abi3 wheels by @​aminalaee in aminalaee/uuid-utils#234

Full Changelog: aminalaee/uuid-utils@1.1.0...1.2.0

1.1.0

What's Changed

• Build Python 3.15 and 3.15t wheels by @​shaanmajid in aminalaee/uuid-utils#227
• Upgrade uuid and rand crates by @​aminalaee in aminalaee/uuid-utils#228

Full Changelog: aminalaee/uuid-utils@1.0.0...1.1.0

1.0.0

Highlights

1.0 realigns uuid6, uuid7, and uuid8 with the signatures Python 3.14 added to the standard library, so code written against uuid works unchanged here. This is the intentional break the 0.x line was frozen for — the legacy signatures are removed.

Breaking changes

	0.x	1.0
uuid6	uuid6(node=None, timestamp=None, nanos=None)	uuid6(node=None, clock_seq=None)
uuid7	uuid7(timestamp=None, nanos=None)	uuid7(*, nanoseconds=None)
uuid8	uuid8(bytes)	uuid8(a=None, b=None, c=None)

uuid1, uuid3, uuid4, uuid5 and the UUID type are unchanged. (#181, #183, #184)

Migration

# uuid7 — 1.0 takes nanoseconds directly, no splitting
uuid_utils.uuid7(seconds, nanos)                                # 0.x
uuid_utils.uuid7(nanoseconds=seconds * 1_000_000_000 + nanos)   # 1.0
uuid8 — three integer blocks of 48 | 12 | 62 bits
uuid_utils.uuid8(b"1234567812345678")                           # 0.x
n = int.from_bytes(b"1234567812345678", "big")                  # 1.0
uuid_utils.uuid8(n >> 80, (n >> 64) & 0xFFF, n & 0x3FFF_FFFF_FFFF_FFFF)
uuid6 — drop the timestamp
uuid_utils.uuid6(node, timestamp, nanos)                        # 0.x
uuid_utils.uuid6(node, clock_seq)                               # 1.0

Staying on 0.x

If you pin uuid-utils<1.0 nothing here reaches you. The 0.x line stays maintained for

... (truncated)

Commits

• f6f2cc5 Version 1.2.0 (#235)
• 36981d9 build: abi3 wheels (#234)
• e518337 Version 1.1.0 (#231)
• bcce2ca Upgrade uuid and rand crates (#228)
• d747a31 Build Python 3.15 and 3.15t wheels (#227)
• 351101b Bump uraimo/run-on-arch-action from 3.2.0 to 3.2.1 (#225)
• 588f986 Bump the python-packages group with 3 updates (#226)
• 661b3fb Version 1.0.0 (#222)
• fa3c05c fix: set the RFC 4122 variant when version is passed (#218)
• 673ec04 chore: bump pyo3 to 0.29.2 and uuid to 1.26.0 (#217)
• Additional commits viewable in compare view

Updates alembic from 1.18.5 to 1.20.1

Release notes

Sourced from alembic's releases.

1.20.1

Released: October 21, 2026

bug

• [bug] [autogenerate] Fixed issue where a table or column comment set to an empty string would cause autogenerate to detect a comment change on every run. As most backends, including PostgreSQL, MySQL, MariaDB and Oracle, don't store an empty string comment distinctly from no comment, autogenerate now treats an empty string comment the same as None when comparing comments. Additionally, an empty string comment is now rendered in op.create_table() and op.add_column() directives, where it was previously omitted. Pull request courtesy vineoy.

  References: #1085

• [bug] [autogenerate] [postgresql] Fixed rendering of the PostgreSQL ~sqlalchemy.dialects.postgresql.DOMAIN type in autogenerated migration scripts. Previously the type was rendered using repr(), which omitted the check, not_null, default, collation, constraint_name, schema and create_type arguments and did not apply a dialect prefix to the underlying data type. The full set of arguments is now rendered and the underlying data type is rendered using the standard type-rendering logic. Pull request courtesy Sebastian Cao.

  References: #1360

• [bug] [autogenerate] [postgresql] Fixed false-positive "Computed default cannot be modified" warning emitted during autogenerate when comparing PostgreSQL Computed columns whose reflected SQL expression includes type cast specifiers such as ::regconfig or ::text, which PostgreSQL adds to the expression as...

  Description has been truncated

[czpython]

@dependabot rebase