chore(deps): bump the minor-and-patch group across 1 directory with 15 updates

[dependabot]

Bumps the minor-and-patch group with 15 updates in the /python directory:

Package	From	To
pytest	9.0.3	9.1.1
pytest-rerunfailures	16.2	16.5
litellm	1.85.0	1.96.2
pytest-asyncio	1.3.0	1.4.0
pydantic-settings	2.14.2	2.15.0
langwatch	1.0.0	1.2.0
twilio	9.10.9	9.11.0
fastapi	0.136.1	0.141.1
uvicorn	0.47.0	0.52.3
google-genai	2.4.0	2.18.1
elevenlabs	2.49.0	2.64.0
pre-commit	4.6.0	4.6.2
pyright	1.1.409	1.1.411
streamlit	1.57.0	1.61.1
plotly	6.7.0	6.9.0

Updates pytest from 9.0.3 to 9.1.1

Release notes

Sourced from pytest's releases.

9.1.1

pytest 9.1.1 (2026-06-19)

Bug fixes

• #14220: Fixed a logic bug in pytest.RaisesGroup which would might cause it to display incorrect "It matches FooError() which was paired with BarError" messages.
• #14591: Fixed a regression in pytest 9.1.0 which caused overriding a parametrized fixture with an indirect @​pytest.mark.parametrize to fail with "duplicate parametrization of '<fixture name>'".
• #14606: Fixed list-item typing errors from mypy in @pytest.mark.parametrize <pytest.mark.parametrize ref> argvalues parameter.
• #14608: Fixed a regression in pytest 9.1.0 where conftest.py files located in <invocation dir>/test* were no longer loaded as initial conftests when invoked without arguments. This could cause certain hooks (like pytest_addoption) in these files to not fire.

9.1.0

pytest 9.1.0 (2026-06-13)

Removals and backward incompatible breaking changes

• #14533: When using --doctest-modules, autouse fixtures with module, package or session scope that are defined inline in Python test modules (not plugins or conftests) will now possibly execute twice.

  If this is undesirable, move the fixture definition to a conftest.py file if possible.

  Technical explanation for those interested: When using --doctest-modules, pytest possibly collects Python modules twice, once as pytest.Module and once as a DoctestModule (depending on the configuration). Due to improvements in pytest's fixture implementation, if e.g. the DoctestModule collects a fixture, it is now visible to it only, and not to the Module. This means that both need to register the fixtures independently.

Deprecations (removal in next major release)

• #10819: Added a deprecation warning for class-scoped fixtures defined as instance methods (without @classmethod). Such fixtures set attributes on a different instance than the test methods use, leading to unexpected behavior. Use @classmethod decorator instead -- by yastcher.

  See 10819 and 14011.

• #12882: Calling request.getfixturevalue() <pytest.FixtureRequest.getfixturevalue> during teardown to request a fixture that was not already requested is now deprecated and will become an error in pytest 10.

  See dynamic-fixture-request-during-teardown for details.

• #13409: Using non-~collections.abc.Collection iterables (such as generators, iterators, or custom iterable objects) for the argvalues parameter in @pytest.mark.parametrize <pytest.mark.parametrize ref> and metafunc.parametrize <pytest.Metafunc.parametrize> is now deprecated.

  These iterables get exhausted after the first iteration, leading to tests getting unexpectedly skipped in cases such as running pytest.main() multiple times, using class-level parametrize decorators, or collecting tests multiple times.

  See parametrize-iterators for details and suggestions.

• #13946: The private config.inicfg attribute is now deprecated. Use config.getini() <pytest.Config.getini> to access configuration values instead.

  See config-inicfg for more details.

• #14004: Passing baseid to ~pytest.FixtureDef or nodeid strings to fixture registration APIs is now deprecated. These are internal pytest APIs that are used by some plugins.

... (truncated)

Commits

• cf470ec Prepare release version 9.1.1
• e0c8ce6 Merge pull request #14625 from pytest-dev/patchback/backports/9.1.x/a07c31a97...
• 1b82d16 Merge pull request #14624 from pytest-dev/patchback/backports/9.1.x/b375b79ec...
• 501c4bc Merge pull request #14596 from bluetech/doc-classmethod
• b61f588 Merge pull request #14622 from chrisburr/fix-14608-initial-conftest-test-subdir
• 9a567e0 [automated] Update plugin list (#14617) (#14618)
• ef8b299 Merge pull request #14620 from pytest-dev/patchback/backports/9.1.x/680f9f3ed...
• 66abd07 Merge pull request #14220 from bysiber/fix-stale-iexp-raisesgroup
• 79fbf93 Merge pull request #14612 from pytest-dev/patchback/backports/9.1.x/974ed48b6...
• 0d312eb Merge pull request #14611 from bluetech/parametrize-argvalues-typing
• Additional commits viewable in compare view

Updates pytest-rerunfailures from 16.2 to 16.5

Changelog

Sourced from pytest-rerunfailures's changelog.

16.5 (2026-08-13)

Features ++++++++

• Add --max-suite-reruns option to cap the total number of reruns across the entire test suite. Once the limit is reached, no further reruns occur regardless of per-test --reruns or @pytest.mark.flaky settings. ([#298](https://github.com/pytest-dev/pytest-rerunfailures/issues/298) <https://github.com/pytest-dev/pytest-rerunfailures/issues/298>_)

Bug Fixes +++++++++

• Create a new test class instance for each rerun. Previously the instance of the failed attempt was reused, so state stored on self leaked into the rerun and broke test isolation. Fixtures cached at class scope or higher are still not re-executed. ([#268](https://github.com/pytest-dev/pytest-rerunfailures/issues/268) <https://github.com/pytest-dev/pytest-rerunfailures/issues/268>_)
• Prevent a rerun when a fixture teardown raises an error matching --rerun-except. Previously only the error from the current test stage was considered, so a --rerun-except-matching error raised during teardown was ignored and the test was rerun anyway. ([#270](https://github.com/pytest-dev/pytest-rerunfailures/issues/270) <https://github.com/pytest-dev/pytest-rerunfailures/issues/270>_)

16.4 (2026-07-01)

Breaking changes ++++++++++++++++

• Drop support for pytest 8.1. Minimum pytest version is now 8.2.

Features ++++++++

• Add support for pytest 9.1.

• Rerun tests with failed subtests. This feature is only available on pytest 9.0 and later. The pytest-subtests plugin is not supported. Fixes [#315](https://github.com/pytest-dev/pytest-rerunfailures/issues/315) <https://github.com/pytest-dev/pytest-rerunfailures/issues/315>_.

• Add --reruns-delay-backoff-factor option (and the matching reruns_delay_backoff_factor marker kwarg / ini setting) to grow the rerun delay after each attempt for an exponential backoff. The delay before the n-th re-run is reruns_delay * reruns_delay_backoff_factor ** (n - 1). The default factor is 1.0, so existing behaviour (a constant delay) is unchanged.

... (truncated)

Commits

• 88291f7 Preparing release 16.5
• 81141e0 Switch change log management to towncrier (#341)
• 6df6fb5 Create a fresh test class instance for each rerun (#340)
• 0440e21 fix: prevent rerun when teardown error matches --rerun-except (#338)
• 5fc2d79 feat: add --max-suite-reruns option to cap total reruns across suite (#332)
• 5fc495a Bump actions/setup-python from 6 to 7 in the actions group (#339)
• 1087cc2 Back to development: 16.5
• e5a86e5 Preparing release 16.4
• 4ddc213 Add --reruns-delay-backoff-factor for exponential rerun backoff (#336)
• 483fce7 Bump the actions group with 2 updates (#337)
• Additional commits viewable in compare view

Updates litellm from 1.85.0 to 1.96.2

Release notes

Sourced from litellm's releases.

v1.96.2

Verify Docker Image Signature

All LiteLLM Docker images are signed with cosign. Every release is signed with the same key introduced in commit 0112e53.

Verify using the pinned commit hash (recommended):

A commit hash is cryptographically immutable, so this is the strongest way to ensure you are using the original signing key:

cosign verify \
  --key https://raw.githubusercontent.com/BerriAI/litellm/0112e53046018d726492c814b3644b7d376029d0/cosign.pub \
  ghcr.io/berriai/litellm:v1.96.2

Verify using the release tag (convenience):

Tags are protected in this repository and resolve to the same key. This option is easier to read but relies on tag protection rules:

cosign verify \
  --key https://raw.githubusercontent.com/BerriAI/litellm/v1.96.2/cosign.pub \
  ghcr.io/berriai/litellm:v1.96.2

Expected output:

The following checks were performed on each of these signatures:
  - The cosign claims were validated
  - The signatures were verified against the specified public key

---

What's Changed

• chore(release): backport proxy request-handling maintenance and refresh runtime deps for 1.96.1 by @​yuneng-berri in BerriAI/litellm#36494
• bump: version 1.96.1 → 1.96.2 (1.96.1 burned by the PyPI storage failure) by @​yuneng-berri in BerriAI/litellm#36570

Full Changelog: BerriAI/litellm@v1.96.0...v1.96.2

v1.96.0

Verify Docker Image Signature

All LiteLLM Docker images are signed with cosign. Every release is signed with the same key introduced in commit 0112e53.

Verify using the pinned commit hash (recommended):

A commit hash is cryptographically immutable, so this is the strongest way to ensure you are using the original signing key:

... (truncated)

Commits

• 83d6d84 Merge pull request #36570 from BerriAI/litellm_bump_version_1_96_2
• 1f4685e chore: refresh uv.lock for 1.96.2
• 256c496 bump: version 1.96.1 → 1.96.2
• af094fa Merge pull request #36494 from BerriAI/litellm_backport_1_96_x_bp196
• dc6d1d8 chore: refresh uv.lock for 1.96.1
• 3605e38 bump: version 1.96.0 → 1.96.1
• 697fac9 chore(deps): drop the pypdf scanner exceptions cleared by 6.15.0
• 48d572b chore(deps): bump pypdf to 6.15.0
• 820f247 Merge pull request #36011 from BerriAI/litellm_maint_batch_2026_07
• 8843766 Merge pull request #36320 from BerriAI/litellm_/litellm-1-96-0-release-ui-48fbeb
• Additional commits viewable in compare view

Updates pytest-asyncio from 1.3.0 to 1.4.0

Release notes

Sourced from pytest-asyncio's releases.

pytest-asyncio v1.4.0

1.4.0 - 2026-05-26

Deprecated

• Overriding the event_loop_policy fixture is deprecated. Use the pytest_asyncio_loop_factories hook instead. (#1419)

Added

• Added the pytest_asyncio_loop_factories hook to parametrize asyncio tests with custom event loop factories.

  The hook returns a mapping of factory names to loop factories, and pytest.mark.asyncio(loop_factories=[...]) selects a subset of configured factories per test. When a single factory is configured, test names are unchanged.

  Synchronous @pytest_asyncio.fixture functions now see the correct event loop when custom loop factories are configured, even when test code disrupts the current event loop (e.g., via asyncio.run() or asyncio.set_event_loop(None)). (#1164)

Changed

• Improved the readability of the warning message that is displayed when asyncio_default_fixture_loop_scope is unset (#1298)
• Only import asyncio.AbstractEventLoopPolicy for type checking to avoid raising a DeprecationWarning. (#1394)
• Updated minimum supported pytest version to v8.4.0. (#1397)

Fixed

• Fixed a ResourceWarning: unclosed event loop warning that could occur when a synchronous test called asyncio.run() or otherwise unset the current event loop after pytest-asyncio had run an async test or fixture. (#724)

Notes for Downstream Packagers

• Added dependency on sphinx-tabs >= 3.5 to organize documentation examples into tabs. (#1395)

pytest-asyncio v1.4.0a2

1.4.0a2 - 2026-05-02

Deprecated

• Overriding the event_loop_policy fixture is deprecated. Use the pytest_asyncio_loop_factories hook instead. (#1419)

Added

• Added the pytest_asyncio_loop_factories hook to parametrize asyncio tests with custom event loop factories.

  The hook returns a mapping of factory names to loop factories, and pytest.mark.asyncio(loop_factories=[...]) selects a subset of configured factories per test. When a single factory is configured, test names are unchanged on pytest 8.4+.

  Synchronous @pytest_asyncio.fixture functions now see the correct event loop when custom loop factories are configured, even when test code disrupts the current event loop (e.g., via asyncio.run() or asyncio.set_event_loop(None)). (#1164)

Changed

• Improved the readability of the warning message that is displayed when asyncio_default_fixture_loop_scope is unset (#1298)
• Only import asyncio.AbstractEventLoopPolicy for type checking to avoid raising a DeprecationWarning. (#1394)

... (truncated)

Commits

• 6e14cd2 chore: Prepare release of v1.4.0.
• 4b900fb Build(deps): Bump codecov/codecov-action from 6.0.0 to 6.0.1
• ab9f632 Build(deps): Bump zipp from 3.23.1 to 4.1.0
• a56fc77 Build(deps): Bump hypothesis from 6.152.6 to 6.152.8
• e8bae9b Build(deps): Bump requests from 2.34.0 to 2.34.2
• fc43340 Build(deps): Bump idna from 3.14 to 3.15
• 762eaf5 Build(deps): Bump jaraco-functools from 4.4.0 to 4.5.0
• b62e222 Build(deps): Bump click from 8.3.3 to 8.4.0
• 9190447 Build(deps): Bump pydantic from 2.13.3 to 2.13.4
• 82a393c ci: Remove unnecessary debug output.
• Additional commits viewable in compare view

Updates pydantic-settings from 2.14.2 to 2.15.0

Release notes

Sourced from pydantic-settings's releases.

v2.15.0

Highlights

Behavior changes

• case_sensitive now applies to init kwargs and config-file sources (#900). InitSettingsSource and the JSON/TOML/YAML config sources previously ignored case_sensitive. Since it defaults to False, case-insensitive matching is now the default for these sources — e.g. Settings(TeSt=...) now populates a test field where it previously did not. Nested keys are still matched case-sensitively.
• Fields with unresolved forward references now emit a warning (#901). Settings sources can silently fail to resolve such fields; they now raise IncompleteFieldDefinitionWarning telling you to call model_rebuild(). If you have filterwarnings = error configured, this may surface as a new failure.
• Non-JSON env values for strict fields now raise ValidationError (#926) instead of a less specific error.

New features

• Show environment variable names in CLI help via cli_show_env_vars=True (#860), so generated --help output doubles as configuration documentation.
• PYDANTIC_SETTINGS_DEBUG for debugging settings resolution (#906, #913). Set it to a truthy value with DEBUG logging enabled to see each source's contribution in priority order, which source won for each value, and which env_file/secret files were probed, loaded, or skipped — the long-standing "why isn't my .env being picked up?" question.
• toml_table_header for regular TOML files (#882, #886, #887), letting you root settings at a nested table in any TOML file, not just pyproject.toml.
• Traversable support for JSON/TOML/YAML file sources (#902), so you can load config packaged inside a distribution — including files inside a zip or wheel — via importlib.resources.files(...) without casting to Path.
• GCP: project_id can come from an earlier settings source (#878), rather than only from the constructor or GOOGLE_CLOUD_PROJECT.

Bug fixes

• Fix env vars not loading on Windows with case_sensitive=True (#894). Windows upper-cases os.environ keys, so fields raised Field required instead of picking up their values.
• Read secret files as UTF-8 instead of the platform locale encoding (#917). On Windows code pages such as cp1252 this silently corrupted non-ASCII secrets.
• Fix AliasPath on nested model fields not JSON-decoding env values (#898).
• Fix case-insensitive matching for optional nested models (#905).
• Fix dotenv extras being wrongly claimed by a complex field sharing a name prefix (#912) — e.g. dbx_token being swallowed by a db: dict field.
• Fix nested_model_default_partial_update=True corrupting discriminated unions (#876).
• Fix Secret subclasses crashing when loaded from the environment (#920).
• Fix enum names not parsing through nested annotations such as Optional[Annotated[MyEnum, ...]] with env_parse_enums=True (#910).
• An empty yaml_config_section now falls back to defaults instead of raising AttributeError: 'NoneType' object has no attribute 'keys' (#914).
• NestedSecretsSettingsSource no longer follows symlinks pointing outside secrets_dir (#889).
• GCP: skip the list_secrets call when case_sensitive=True (#862), lowering the required IAM permissions to just roles/secretmanager.secretAccessor.
• AWS: types-boto3[secretsmanager] is no longer required at runtime (#880).

Documentation

• Document JSON parsing of complex env values, plus a comma-separated-values recipe (#919).
• Recommend an async settings loading pattern (#908).
• Clarify behavior when an unprefixed value is present in a dotenv file (#895).
• Clarify environment variable helper descriptions (#867) and fix assorted typos (#904).

What's Changed

• Update documentation link for Pydantic settings by @​hramezani in pydantic/pydantic-settings#863
• Bump the python-packages group with 4 updates by @​dependabot[bot] in pydantic/pydantic-settings#865
• docs: clarify environment variable helper descriptions by @​vip892766gma in pydantic/pydantic-settings#867
• Bump the python-packages group with 4 updates by @​dependabot[bot] in pydantic/pydantic-settings#870
• Bump the python-packages group with 4 updates by @​dependabot[bot] in pydantic/pydantic-settings#875
• Skip list_secrets call when case_sensitive=True by @​ecerulm in pydantic/pydantic-settings#862
• GoogleSecretManagerSettingsSource: read project_id from previous sources by @​ecerulm in pydantic/pydantic-settings#878

... (truncated)

Commits

• f725ca1 Prepare release 2.15.0 (#930)
• 28f35c2 Bump the python-packages group with 4 updates (#929)
• 9056db0 test: move function-local imports to the top of test modules (#927)
• f077e3a fix: raise ValidationError for non-JSON env values on strict fields (#926)
• ae25d70 fix: treat Secret subclasses as non-complex fields (#716) (#920)
• 798dcea Bump the python-packages group with 4 updates (#924)
• a190041 Bump the github-actions group with 4 updates (#925)
• 5d93332 Bump the python-packages group with 4 updates (#921)
• d2fdeda fix: read secret files as UTF-8 instead of the locale encoding (#917)
• 2256a4e Bump the python-packages group with 3 updates (#915)
• Additional commits viewable in compare view

Updates langwatch from 1.0.0 to 1.2.0

Changelog

Sourced from langwatch's changelog.

1.2.0 (2025-10-18)

Features

• add filters on series for custom graphs (#705) (b200586)
• add percentage to series (#709) (c6e63df)
• added automatic country detection to phone input (#714) (82d3fe0)
• new onboarding flow (#686) (26d9c8d)

Bug Fixes

• failing go test with gpt5 update (bc16d63)
• onboarding types to align with crm (#727) (8b7f9b2)
• refactor to stop re-rendering causing input focus mayhem (#729) (9981533)
• release please was broken (4e09652)
• release please was broken with missing permissions (#723) (4e09652)
• remove usage stats log (#725) (f113b0c)
• type errors in langwatch app (#716) (f6cc1c8)
• updates for release please (#711) (d88597c)

Miscellaneous

• added onboarding signout button (#721) (2741e96)
• new onboarding analytics (#720) (af4ebf0)
• refactor onboarding component structure (#715) (3900c1b)
• use release specific token (#717) (c8acb69)

1.1.1 (2025-10-13)

Bug Fixes

• add bodyparser limit to all otel inbound endpoints (#707) (d9ce8bb)
• find local prompt (#700) (ab42400)
• improve performance on evaluations table with virtualized grid (#701) (b5eb7d1)
• reduce cache count to 5 min to avoid blowups, and move histograms to common place (589797d)

1.1.0 (2025-10-13)

Features

• add support for otel /metrics endpoint for genai metrics (#680) (14bec0d)
• add thread evals (#677) (e89700b)

Bug Fixes

... (truncated)

Commits

• 521c3e1 chore: release main (#712)
• 9981533 fix: refactor to stop re-rendering causing input focus mayhem (#729)
• 7961a03 test: create CI server for SDK e2e tests (#719)
• 8b7f9b2 fix: onboarding types to align with crm (#727)
• f113b0c fix: remove usage stats log (#725)
• af4ebf0 chore: new onboarding analytics (#720)
• 4e09652 fix: release please was broken with missing permissions (#723)
• 2741e96 chore: added onboarding signout button (#721)
• bc16d63 test: failing go test with gpt5 update (#718)
• c8acb69 chore: use release specific token (#717)
• Additional commits viewable in compare view

Updates twilio from 9.10.9 to 9.11.0

Release notes

Sourced from twilio's releases.

9.11.0

Release Notes

Library - Fix

• [PR #929](twilio/twilio-python#929): mock HTTP session in TestUserAgentClients to avoid live network calls. Thanks to @​shrutiburman!

Twiml

• Remove <Assistant> noun from <Connect> verb as part of the AI Assistants deprecation (breaking change)
• Add passports attribute to <Dial> verb for SHAKEN/STIR passport passthrough

Accounts

• Add SuppressEmailNotification parameter to the Secondary Auth Token and Auth Token promotion endpoints. Set it to true to suppress the email notification sent to account owners and administrators. Defaults to false, preserving existing behavior.
• Add SMS Pumping Protection GET and POST API

Ai

• Removing ai workbench apis

Api

• Add missing uri property to the twiml_session resource

Data-ingress

• 2026-08-07

• Removed 1 API path:
• /v1/DataQuery (Realtime DataQuery)

• 2026-07-07

• Added 1 new API path (data plane):
• /v1/DataQuery (Realtime DataQuery)

• 2026-06-17

• Content updates:
• Added properties to OAuthJWTBearerCredentials: privateKey, privateKeyPassphrase

• 2026-06-12

• Added 16 new path(s):
• /v1/DataSyncs/{syncId} (FetchDataSync)
• /v1/CloudAppSources/{sourceId}/Objects (ListCloudAppObjects)
• /v1/WarehouseSources/{sourceId}/Preview (CreateWarehousePreview)
• /v1/WarehouseSources/{sourceId}/Preview/{operationId} (FetchWarehousePreview)
• /v1/DataSample/{operationId} (FetchDataSample)
• /v1/ControlPlane/CloudAppSources/{sourceId} (FetchCloudAppSource, PatchCloudAppSource, DeleteCloudAppSource)
• /v1/ControlPlane/CloudAppSources/{sourceId}/Datasets (ListCloudAppDatasets, CreateCloudAppDataset)
• /v1/ControlPlane/CloudAppSources/{sourceId}/Datasets/{datasetId} (FetchCloudAppDataset, PatchCloudAppDataset, DeleteCloudAppDataset)
• /v1/ControlPlane/WarehouseSources/{sourceId} (FetchWarehouseSource, PatchWarehouseSource, DeleteWarehouseSource)
• /v1/ControlPlane/WarehouseSources/{sourceId}/Datasets (ListWarehouseDatasets, CreateWarehouseDataset)
• ...and 6 more paths
• Removed 16 path(s):
• /v1/DataSyncs/{SyncId} (FetchDataSync)
• /v1/CloudAppSources/{SourceId}/Objects (ListCloudAppObjects)
• /v1/WarehouseSources/{SourceId}/Preview (CreateWarehousePreview)
• /v1/WarehouseSources/{SourceId}/Preview/{OperationId} (FetchWarehousePreview)
• /v1/DataSample/{OperationId} (FetchDataSample)
• /v1/ControlPlane/CloudAppSources/{SourceId} (FetchCloudAppSource, PatchCloudAppSource, DeleteCloudAppSource)

... (truncated)

Changelog

Sourced from twilio's changelog.

[2026-08-11] Version 9.11.0

Library - Fix

• [PR #929](twilio/twilio-python#929): mock HTTP session in TestUserAgentClients to avoid live network calls. Thanks to @​shrutiburman!

Twiml

• Remove <Assistant> noun from <Connect> verb as part of the AI Assistants deprecation (breaking change)
• Add passports attribute to <Dial> verb for SHAKEN/STIR passport passthrough

Accounts

• Add SuppressEmailNotification parameter to the Secondary Auth Token and Auth Token promotion endpoints. Set it to true to suppress the email notification sent to account owners and administrators. Defaults to false, preserving existing behavior.
• Add SMS Pumping Protection GET and POST API

Ai

• Removing ai workbench apis

Api

• Add missing uri property to the twiml_session resource

Data-ingress

• 2026-08-07

• Removed 1 API path:
• /v1/DataQuery (Realtime DataQuery)

• 2026-07-07

• Added 1 new API path (data plane):
• /v1/DataQuery (Realtime DataQuery)

• 2026-06-17

• Content updates:
• Added properties to OAuthJWTBearerCredentials: privateKey, privateKeyPassphrase

• 2026-06-12

• Added 16 new path(s):
• /v1/DataSyncs/{syncId} (FetchDataSync)
• /v1/CloudAppSources/{sourceId}/Objects (ListCloudAppObjects)
• /v1/WarehouseSources/{sourceId}/Preview (CreateWarehousePreview)
• /v1/WarehouseSources/{sourceId}/Preview/{operationId} (FetchWarehousePreview)
• /v1/DataSample/{operationId} (FetchDataSample)
• /v1/ControlPlane/CloudAppSources/{sourceId} (FetchCloudAppSource, PatchCloudAppSource, DeleteCloudAppSource)
• /v1/ControlPlane/CloudAppSources/{sourceId}/Datasets (ListCloudAppDatasets, CreateCloudAppDataset)
• /v1/ControlPlane/CloudAppSources/{sourceId}/Datasets/{datasetId} (FetchCloudAppDataset, PatchCloudAppDataset, DeleteCloudAppDataset)
• /v1/ControlPlane/WarehouseSources/{sourceId} (FetchWarehouseSource, PatchWarehouseSource, DeleteWarehouseSource)
• /v1/ControlPlane/WarehouseSources/{sourceId}/Datasets (ListWarehouseDatasets, CreateWarehouseDataset)
• ...and 6 more paths
• Removed 16 path(s):
• /v1/DataSyncs/{SyncId} (FetchDataSync)
• /v1/CloudAppSources/{SourceId}/Objects (ListCloudAppObjects)
• /v1/WarehouseSources/{SourceId}/Preview (CreateWarehousePreview)
• /v1/WarehouseSources/{SourceId}/Preview/{OperationId} (FetchWarehousePreview)
• /v1/DataSample/{OperationId} (FetchDataSample)
• /v1/ControlPlane/CloudAppSources/{SourceId} (FetchCloudAppSource, PatchCloudAppSource, DeleteCloudAppSource)
• /v1/ControlPlane/CloudAppSources/{SourceId}/Datasets (ListCloudAppDatasets, CreateCloudAppDataset)

... (truncated)

Commits

• 306691e Fix tag validation regex in deploy.yml (#954)
• a7c1450 Update Python version matrix in deploy.yml (#953)
• eba3466 [Librarian] Regenerated @ f443c9dfa233e41d0e61c9ed6ca2b162467a08b5 89762bc866...
• fbdfe4e Update deployment trigger to all tags (#950)
• 3a5e24d Comment out docs generation verification step (#952)
• 89689b2 handle-blank-response-202 (#949)
• 3b82ae1 Remove assistant apis cluster test (#948)
• 184b583 fix: updates to release process (#941)
• becbfc5 removed oauth beta maturity from readme (#943)
• ecf51ac Add test and release gate workflow (#940)
• Additional commits viewable in compare view

Updates fastapi from 0.136.1 to 0.141.1

Release notes

Sourced from fastapi's releases.

0.141.1

Fixes

• 🐛 Fix support for background tasks and headers from dependencies in app.frontend(). PR #16105 by @​tiangolo.

Docs

• 📝 Document FASTAPI_ENV in FastAPI CLI guide. PR #16104 by @​tiangolo.

0.141.0

Features

• ✨ Add app.frontend(check_dir="auto"), to make local development more convenient with fastapi dev. PR #16102 by @​tiangolo.

0.140.13

Fixes

• 🐛 Fix status_code being ignored for SSE and JSONL streaming endpoints. PR #15937 by @​SAURABHSALVE.

Docs

• 📝 Fix format_sse_event docstring rendering of \n\n terminator. PR #15613 by @​AshNicolus.
• 📝 Add API reference page for fastapi.sse. PR #15930 by @​SAURABHSALVE.

0.140.12

Fixes

• 🐛 Fix line splitting in format_sse_event to comply with SSE spec. PR #15515 by @​Zawwarsami16.

0.140.11

Fixes

• 🐛 Fix response_model_* params ignored for non-generator endpoints with Iterable[..] return type. PR #15093 by @​YuriiMotov.

0.140.10

Fixes

• 🐛 Fix handling sequences with nested Annotated types. PR #14874 by @​YuriiMotov.

Internal

• 🐛 Accept any base test failure as regression. PR #16092 by @​tiangolo.
• 🐛 Preserve pytest exit code in regression check. PR #16091 by @​tiangolo.
• ✅ Test PR regressions against base code. PR #16090 by @​tiangolo.

0.140.9

Fixes

• 🐛 Fix exclude_defaults not propagated to dict keys and values in jsonable_encoder. PR #16043 by @​MBGrao.

... (truncated)

Commits

• 95f8322 🔖 Release version 0.141.1 (#16106)
• f137944 📝 Update release notes
• d623544 🐛 Fix support for background tasks and headers from dependencies in `app.fron...
• 1d211b9 📝 Update release notes
• 8a1f876 📝 Document FASTAPI_ENV in FastAPI CLI guide (#16104)
• c7e7b65 🔖 Release version 0.141.0 (#16103)
• 6bceb84 📝 Update release notes
• 5429fed ✨ Add app.frontend(check_dir="auto"), to make local development more conven...
• 628663f 🔖 Release version 0.140.13 (#16096)
• 0b54fd0 📝 Update release notes
• Additional commits viewable in compare view

Updates uvicorn from 0.47.0 to 0.52.3

Release notes

Sourced from uvicorn's releases.

Version 0.52.3

Changed

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

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

Version 0.52.2

Fixed

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

Full Changelog: Kludex/uvicorn@0.52.1...0.52.2

Version 0.52.1

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)
• Remove duplicate Content-Type and Content-Length headers from WebSocket denial responses on the websockets-sansio implementation, and deliver non-UTF-8 denial bodies intact (#3041)

Full Changelog:

[langwatch-agent]

Static review of this external dependency update: the diff is limited to the Python lockfile and preserves pinned artifact hashes. The only failed required workflow was abandoned before tests when GitHub returned 429 while downloading the pinned paths-filter action, so it is not evidence of a branch failure. I found no blocking issue in the current head.

LangWatch-Review: verdict=clean sha=52205e957a3495660a1554e9b47877c9cc6239ee p0=0 p1=0 p2=0 p3=0

[0xdeafcafe]

@dependabot rebase

[github-actions]

Automated low-risk assessment

This PR was evaluated against the repository's Low-Risk Pull Requests procedure and does not qualify as low risk.

This PR's diff could not be evaluated automatically: Diff too large for automated evaluation (108918 chars exceeds 100000-char limit). Manual review required.

This PR requires a manual review before merging.

[0xdeafcafe]

Auto-approved: dependency-only bump (dependabot), all required checks green.

[0xdeafcafe]

@dependabot rebase

[langwatch-agent]

External static review: no blocking concern found in the current diff. I did not execute branch code, install dependencies, or run contributor-provided scripts. Residual risk: runtime behavior remains covered by the repository CI.

LangWatch-Review: verdict=clean sha=ab559c1b1735744f38057e0e23634b7b02a3c4d0 p0=0 p1=0 p2=0 p3=0

[langwatch-agent]

External static review: no blocking concern found in the current diff. I did not execute branch code, install dependencies, or run contributor-provided scripts. Residual risk: runtime behavior remains covered by the repository CI.

LangWatch-Review: verdict=clean sha=ab559c1b1735744f38057e0e23634b7b02a3c4d0 p0=0 p1=0 p2=0 p3=0