[dependabot]

Bumps the uv-minor-and-patch group with 12 updates in the / directory:

Package	From	To
fastapi	0.141.1	0.162.0
pydantic	2.13.4	2.14.2
pydantic-settings	2.15.0	2.16.2
opentelemetry-sdk	1.44.0	1.45.2
opentelemetry-exporter-otlp-proto-http	1.44.0	1.45.2
opentelemetry-instrumentation-fastapi	0.65b0	0.66b2
opentelemetry-instrumentation-httpx	0.65b0	0.66b2
nats-py	2.15.0	2.16.0
pytest	9.1.1	9.2.0
pytest-asyncio	1.4.0	1.4.1
ruff	0.16.3	0.17.3
pyright	1.1.411	1.1.414

Updates fastapi from 0.141.1 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 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.15.0 to 2.16.2

Release notes

Sourced from pydantic-settings's releases.

v2.16.1

Highlights

This patch release fixes two CLI regressions introduced in 2.16.0.

Bug fixes

CLI

• Fixed-length tuple positionals such as CliPositionalArg[tuple[int, int]] and NamedTuples are single-valued again (#1069). Since 2.16.0 they were treated as variadic, so a CLI either refused to start with a SettingsError or put the wrong argument into the tuple. Variable-length tuples (tuple[int, ...] and bare Tuple) are still variadic.
• A field typed as an alias of a list of dicts, e.g. type ListOfDict = list[dict[str, int]], accepts a JSON list again (#1049). Since 2.16.0, --xx '[{"a":1},{"b":2}]' was merged into the single dict {"a": 1, "b": 2} and failed validation.

What's Changed

• Harden CI by @​Viicos in pydantic/pydantic-settings#1044
• Keep list of dicts CLI values as lists by @​hramezani in pydantic/pydantic-settings#1049
• Keep fixed-length tuple CLI positionals single-valued by @​hramezani in pydantic/pydantic-settings#1069
• Prepare release 2.16.1 by @​hramezani in pydantic/pydantic-settings#1087
• build(deps): bump the python-packages group with 3 updates by @​dependabot[bot] in pydantic/pydantic-settings#1056

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

v2.16.0

Highlights

Breaking changes and behavior changes

• Python 3.10 is no longer supported (#1003). pydantic-settings now requires Python 3.11+, since 3.10 reaches end of life this month. The tomli fallback is gone in favor of stdlib tomllib; the toml extra is kept as an empty extra so pip install pydantic-settings[toml] keeps working.
• python-dotenv>=1.2.2 is now required (#971) to pick up the fix for CVE-2026-28684.
• Aliases are ignored in every source when validate_by_alias=False (#1033). Env vars, secrets, CLI flags and defaults now use only field names, matching pydantic. An env var named after the alias is now ignored instead of raising extra_forbidden, and the CLI exposes --apple rather than --pomo.
• validation_alias takes precedence over alias (#1038). When the two differ, values from JSON/YAML/TOML files and the CLI were silently ignored; they now load. CLI help lists the validation_alias flag first, and CliApp.serialize emits it.
• CLI case-insensitivity only lowercases registered options (#1036). With case_sensitive=False, args after -- and those captured by CliUnknownArgs keep their case (-Xmx4G no longer becomes -xmx4g). Unrecognized options are now reported as typed (--NOPE instead of --nope).
• JSON and YAML config files are read as UTF-8 by default (#955) instead of the locale encoding, completing the secrets-file fix from 2.15.0. json_file_encoding/yaml_file_encoding still override it.
• Discriminated union defaults are partially updated again (#997). This reverts the 2.15.0 regression with nested_model_default_partial_update=True: the default is only dropped when the incoming value selects a different union member.

New features

• Python 3.15 and pydantic 2.14 support (#1026, #1029, #1022). pydantic 2.14 broke CliApp.run and validate_by_alias=False handling; both are fixed.
• Cached settings instances via Settings.settings_cached() and Settings.settings_clear_cache() (#952). These give you a process-local singleton per settings class without hand-rolling lru_cache wrappers. Calling the class directly still builds a fresh instance.
• AWS Systems Manager Parameter Store source — AWSSystemsManagerSettingsSource (#941). It recursively reads every parameter under an ssm_path, with / mapping onto nested models. Install it with the new aws-systems-manager extra.
• env_file_depth (#940) lets a relative env_file be found in parent directories, mirroring pyproject_toml_depth. This is useful when scripts run from a subdirectory of a monorepo. It defaults to 0, which keeps the current behavior.
• CliVariadicArg for named variadic options (#949, #958). It accepts --param a b c in addition to repeated --param a --param b. Required fields need at least one value.

Bug fixes

CLI

... (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 opentelemetry-sdk from 1.44.0 to 1.45.2

Release notes

Sourced from opentelemetry-sdk's releases.

Version 1.45.2/0.66b2

This is a patch release on the previous 1.45.1/0.66b1 release, fixing the issue(s) below.

Added

• opentelemetry-sdk, opentelemetry-configuration, opentelemetry-exporter-prometheus: enforce metric cardinality limits (default 2000) with the otel.metric.overflow attribute, configurable through View(aggregation_cardinality_limit=...), reader cardinality_limits and declarative configuration (#5809)

Fixed

• opentelemetry-api: limit traceparent header length to 512 characters in TraceContextTextMapPropagator during extraction (#5818)

Version 1.45.1/0.66b1

This is a patch release on the previous 1.45.0/0.66b0 release, fixing the issue(s) below.

Fixed

• opentelemetry-api: make AnyValue and AttributeValue explicit type aliases (#5703)
• opentelemetry-sdk: fix thread leak bug in resource initialization logic for long running resource detectors (#5706)
• opentelemetry-exporter-otlp-proto-http: restore requests as the default HTTP transport so proxy environment variables such as HTTPS_PROXY are honored again (#5714)
• opentelemetry-api: fix quadratic time parsing of the tracestate header and discard tracestate headers longer than 8192 characters (#5746)

Version 1.45.0/0.66b0

Added

• opentelemetry-exporter-prometheus: add support to configure Resource attributes as metric labels (#5122)
• infra: add renovate (#5202)
• opentelemetry-api, opentelemetry-sdk: add support for extended attribute values everywhere. (#5266)
• opentelemetry-sdk: wire the top-level log_level field in declarative configuration — when set, maps the OTel SeverityNumber value to a Python logging level and applies it to the opentelemetry logger so SDK internal diagnostics respect the configured severity. (#5351)
• opentelemetry-sdk: add the new stable AlwaysRecordSampler (#5354)
• opentelemetry-configuration, opentelemetry-sdk: wire top-level attribute_limits into per-signal providers via declarative config; add log_record_limits support to LoggerProvider (#5365)
• opentelemetry-exporter-otlp-json-http: add OTLP JSON HTTP exporter package (#5374)
• opentelemetry-api, opentelemetry-sdk: add enabled() support to the Logger API, SDK, and LogRecordProcessor to let instrumentation skip expensive work when logging is disabled (#5380)
• opentelemetry-exporter-otlp-json-file: add OTLP JSON file Docker tests (#5412)
• opentelemetry-configuration: wire the experimental tracer_configurator/development, meter_configurator/development and logger_configurator/development fields into create_tracer_provider, create_meter_provider and create_logger_provider, so per-instrumentation-scope enabled overrides declared in the config file are applied to the provider (previously these fields were parsed but silently discarded). The logger minimum_severity/trace_based fields are not supported by the Python SDK and are ignored with a warning. (#5418)
• docs/examples: add example on how to manually setup the SDK to get SDK metrics (#5449)
• opentelemetry-docker-tests: add Prometheus exporter docker tests (#5457)
• opentelemetry-sdk: count records dropped after shutdown on otel.sdk.processor.{span,log}.processed with error.type=already_shutdown (batch span/log and simple log processors), which the semantic conventions define as a valid value for this metric. (#5509)
• opentelemetry-semantic-conventions: update semantic conventions to v1.44.0 (#5511)
• opentelemetry-sdk: add host.id to the host resource detector (#5653)
• opentelemetry-test-utils: add CapturingSampler to record what samplers receive in instrumentation tests (#5681)

Changed

• Enable PIE (flake8-pie) ruff rule and fix all violations (#5150)
• The public opentelemetry.util.types.AttributeValue type in package opentelemetry-api is being expanded to include None, heterogeneous sequences of primitive types (and nested sequences) as opposed to only homogeneous primitive sequences, and Mappings of strings to any primitive types or sequences/mappings (which themselves must only contain primitive types or sequences/mappings validated the same way). If a bytes type is set as an attribute value in the SDK, it will no longer be utf-8 decoded to a string, instead it will be passed along as is in accordance with the OTEL spec, since bytes is a valid type in the OTLP proto. (#5266)
• opentelemetry-exporter-otlp-proto-http: add a max_request_size argument to the OTLP HTTP exporters (traces, logs, metrics); serialized requests larger than the limit are dropped before sending, measured before compression. Defaults to 64 MiB (enabled); set to 0 to disable. Mirrors opentelemetry-go#8157. (#5369)
• [BREAKING] opentelemetry-api: subclasses of Logger need to implement the enabled method (#5380)
• opentelemetry-exporter-otlp-proto-http: refactor to use shared opentelemetry-exporter-otlp-common and opentelemetry-exporter-http-transport packages and switch default HTTP backend to urllib3 (#5389)
• opentelemetry-sdk: unify logging force_flush timeout defaults to 30000ms (#5438)
• opentelemetry-python: enable Ruff default ruleset and fix auto-fixable lint issues (#5491)

... (truncated)

Changelog

Sourced from opentelemetry-sdk's changelog.

Version 1.45.2/0.66b2 (2026-10-29)

Added

• opentelemetry-sdk, opentelemetry-configuration, opentelemetry-exporter-prometheus: enforce metric cardinality limits (default 2000) with the otel.metric.overflow attribute, configurable through View(aggregation_cardinality_limit=...), reader cardinality_limits and declarative configuration (#5809)

Fixed

• opentelemetry-api: limit traceparent header length to 512 characters in TraceContextTextMapPropagator during extraction (#5818)

Version 1.45.1/0.66b1 (2026-10-06)

Fixed

• opentelemetry-api: make AnyValue and AttributeValue explicit type aliases (#5703)
• opentelemetry-sdk: fix thread leak bug in resource initialization logic for long running resource detectors (#5706)
• opentelemetry-exporter-otlp-proto-http: restore requests as the default HTTP transport so proxy environment variables such as HTTPS_PROXY are honored again (#5714)
• opentelemetry-api: fix quadratic time parsing of the tracestate header and discard tracestate headers longer than 8192 characters (#5746)

Version 1.45.0/0.66b0 (2026-09-25)

Added

• opentelemetry-exporter-prometheus: add support to configure Resource attributes as metric labels (#5122)
• infra: add renovate (#5202)
• opentelemetry-api, opentelemetry-sdk: add support for extended attribute values everywhere. (#5266)
• opentelemetry-sdk: wire the top-level log_level field in declarative configuration — when set, maps the OTel SeverityNumber value to a Python logging level and applies it to the opentelemetry logger so SDK internal

... (truncated)

Commits

• ad75594 [release/v1.45.x-0.66bx] Prepare release 1.45.2/0.66b2 (#5862)
• 78123a2 [release/v1.45.x-0.66bx] Backport metric cardinality limits and traceparent p...
• 14971ce Prepare release 1.45.1/0.66b1 (#5752)
• 44ac26e opentelemetry-sdk: fix thread leak bug in resource initialization logic (#570...
• a2ec3f9 [release/v1.45.x-0.66bx] opentelemetry-exporter-otlp-proto-http: restore requ...
• d5224bf opentelemetry-api: improve performance of tracestate parsing (#5746) (#5749)
• db61173 Declare AnyValue and AttributeValue as explicit type aliases (#5703) (#5750)
• 4f0fcfa Prepare release 1.45.0/0.66b0 (#5690)
• 9406f34 opentelemetry-test-utils: add CapturingSampler for instrumentation tests (#5681)
• 1fe31a9 fix: update W3CBaggagePropagator to properly handle whitespace (#5680)
• Additional commits viewable in compare view

Updates opentelemetry-exporter-otlp-proto-http from 1.44.0 to 1.45.2

Release notes

Sourced from opentelemetry-exporter-otlp-proto-http's releases.

Version 1.45.2/0.66b2

This is a patch release on the previous 1.45.1/0.66b1 release, fixing the issue(s) below.

Added

• opentelemetry-sdk, opentelemetry-configuration, opentelemetry-exporter-prometheus: enforce metric cardinality limits (default 2000) with the otel.metric.overflow attribute, configurable through View(aggregation_cardinality_limit=...), reader cardinality_limits and declarative configuration (#5809)

Fixed

• opentelemetry-api: limit traceparent header length to 512 characters in TraceContextTextMapPropagator during extraction (#5818)

Version 1.45.1/0.66b1

This is a patch release on the previous 1.45.0/0.66b0 release, fixing the issue(s) below.

Fixed

• opentelemetry-api: make AnyValue and AttributeValue explicit type aliases (#5703)
• opentelemetry-sdk: fix thread leak bug in resource initialization logic for long running resource detectors (#5706)
• opentelemetry-exporter-otlp-proto-http: restore requests as the default HTTP transport so proxy environment variables such as HTTPS_PROXY are honored again (#5714)
• opentelemetry-api: fix quadratic time parsing of the tracestate header and discard tracestate headers longer than 8192 characters (#5746)

Version 1.45.0/0.66b0

Added

• opentelemetry-exporter-prometheus: add support to configure Resource attributes as metric labels (#5122)
• infra: add renovate (#5202)
• opentelemetry-api, opentelemetry-sdk: add support for extended attribute values everywhere. (#5266)
• opentelemetry-sdk: wire the top-level log_level field in declarative configuration — when set, maps the OTel SeverityNumber value to a Python logging level and applies it to the opentelemetry logger so SDK internal diagnostics respect the configured severity. (#5351)
• opentelemetry-sdk: add the new stable AlwaysRecordSampler (#5354)
• opentelemetry-configuration, opentelemetry-sdk: wire top-level attribute_limits into per-signal providers via declarative config; add log_record_limits support to LoggerProvider (#5365)
• opentelemetry-exporter-otlp-json-http: add OTLP JSON HTTP exporter package (#5374)
• opentelemetry-api, opentelemetry-sdk: add enabled() support to the Logger API, SDK, and LogRecordProcessor to let instrumentation skip expensive work when logging is disabled (#5380)
• opentelemetry-exporter-otlp-json-file: add OTLP JSON file Docker tests (#5412)
• opentelemetry-configuration: wire the experimental tracer_configurator/development, meter_configurator/development and logger_configurator/development fields into create_tracer_provider, create_meter_provider and create_logger_provider, so per-instrumentation-scope enabled overrides declared in the config file are applied to the provider (previously these fields were parsed but silently discarded). The logger minimum_severity/trace_based fields are not supported by the Python SDK and are ignored with a warning. (#5418)
• docs/examples: add example on how to manually setup the SDK to get SDK metrics (#5449)
• opentelemetry-docker-tests: add Prometheus exporter docker tests (#5457)
• opentelemetry-sdk: count records dropped after shutdown on otel.sdk.processor.{span,log}.processed with error.type=already_shutdown (batch span/log and simple log processors), which the semantic conventions define as a valid value for this metric. (#5509)
• opentelemetry-semantic-conventions: update semantic conventions to v1.44.0 (#5511)
• opentelemetry-sdk: add host.id to the host resource detector (#5653)
• opentelemetry-test-utils: add CapturingSampler to record what samplers receive in instrumentation tests (#5681)

Changed

• Enable PIE (flake8-pie) ruff rule and fix all violations (#5150)
• The public opentelemetry.util.types.AttributeValue type in package opentelemetry-api is being expanded to include None, heterogeneous sequences of primitive types (and nested sequences) as opposed to only homogeneous primitive sequences, and Mappings of strings to any primitive types or sequences/mappings (which themselves must only contain primitive types or sequences/mappings validated the same way). If a bytes type is set as an attribute value in the SDK, it will no longer be utf-8 decoded to a string, instead it will be passed along as is in accordance with the OTEL spec, since bytes is a valid type in the OTLP proto. (#5266)
• opentelemetry-exporter-otlp-proto-http: add a max_request_size argument to the OTLP HTTP exporters (traces, logs, metrics); serialized requests larger than the limit are dropped before sending, measured before compression. Defaults to 64 MiB (enabled); set to 0 to disable. Mirrors opentelemetry-go#8157. (#5369)
• [BREAKING] opentelemetry-api: subclasses of Logger need to implement the enabled method (#5380)
• opentelemetry-exporter-otlp-proto-http: refactor to use shared opentelemetry-exporter-otlp-common and opentelemetry-exporter-http-transport packages and switch default HTTP backend to urllib3 (#5389)
• opentelemetry-sdk: unify logging force_flush timeout defaults to 30000ms (#5438)
• opentelemetry-python: enable Ruff default ruleset and fix auto-fixable lint issues (#5491)

... (truncated)

Changelog

Sourced from opentelemetry-exporter-otlp-proto-http's changelog.

Version 1.45.2/0.66b2 (2026-10-29)

Added

• opentelemetry-sdk, opentelemetry-configuration, opentelemetry-exporter-prometheus: enforce metric cardinality limits (default 2000) with the otel.metric.overflow attribute, configurable through View(aggregation_cardinality_limit=...), reader cardinality_limits and declarative configuration (#5809)

Fixed

• opentelemetry-api: limit traceparent header length to 512 characters in TraceContextTextMapPropagator during extraction (#5818)

Version 1.45.1/0.66b1 (2026-10-06)

Fixed

• opentelemetry-api: make AnyValue and AttributeValue explicit type aliases (#5703)
• opentelemetry-sdk: fix thread leak bug in resource initialization logic for long running resource detectors (#5706)
• opentelemetry-exporter-otlp-proto-http: restore requests as the default HTTP transport so proxy environment variables such as HTTPS_PROXY are honored again (#5714)
• opentelemetry-api: fix quadratic time parsing of the tracestate header and discard tracestate headers longer than 8192 characters (#5746)

Version 1.45.0/0.66b0 (2026-09-25)

Added

• opentelemetry-exporter-prometheus: add support to configure Resource attributes as metric labels (#5122)
• infra: add renovate (#5202)
• opentelemetry-api, opentelemetry-sdk: add support for extended attribute values everywhere. (#5266)
• opentelemetry-sdk: wire the top-level log_level field in declarative configuration — when set, maps the OTel SeverityNumber value to a Python logging level and applies it to the opentelemetry logger so SDK internal

... (truncated)

Commits

• ad75594 [release/v1.45.x-0.66bx] Prepare release 1.45.2/0.66b2 (#5862)
• 78123a2 [release/v1.45.x-0.66bx] Backport metric cardinality limits and traceparent p...
• 14971ce Prepare release 1.45.1/0.66b1 (#5752)
• 44ac26e opentelemetry-sdk: fix thread leak bug in resource initialization logic (#570...
• a2ec3f9 [release/v1.45.x-0.66bx] opentelemetry-exporter-otlp-proto-http: restore requ...
• d5224bf opentelemetry-api: improve performance of tracestate parsing (#5746) (#5749)
• db61173 Declare AnyValue and AttributeValue as explicit type aliases (#5703) (#5750)
• 4f0fcfa Prepare release 1.45.0/0.66b0 (#5690)
• 9406f34 opentelemetry-test-utils: add CapturingSampler for instrumentation tests (#5681)
• 1fe31a9 fix: update W3CBaggagePropagator to properly handle whitespace (#5680)
• Additional commits viewable in compare view

Updates opentelemetry-instrumentation-fastapi from 0.65b0 to 0.66b2

Release notes

Sourced from opentelemetry-instrumentation-fastapi's releases.

Version 1.45.2/0.66b2

This is a patch release on the previous 1.45.1/0.66b1 release, fixing the issue(s) below.

Version 1.45.1/0.66b1

This is a patch release on the previous 1.45.0/0.66b0 release, fixing the issue(s) below.

No significant changes.

Version 1.45.0/0.66b0

Added

• opentelemetry-instrumentation-psycopg2, opentelemetry-instrumentation-psycopg: Add sqlcommenter support for instrument_connection (#4267)
• opentelemetry-instrumentation-fastapi: Document auto-instrumentation setup and HTTP/WebSocket trace propagation opentelemetry-instrumentation: Include the instrumentation README in API docs (#4555)
• opentelemetry-instrumentation-botocore: capture Bedrock prompt cache token usage for converse and converse_stream API (#4615)
• opentelemetry-instrumentation-fastapi: advertise inline type annotations (#4685)
• opentelemetry-instrumentation-kafka-python: Update kafka python instrumentation to support kafka-python>=3 (#4786)
• opentelemetry-instrumentation-mysql: add semantic convention stability opt-in mode tests (#4810)
• opentelemetry-instrumentation-aiopg: Add DB client operation duration and returned rows metrics. (#4826)
• opentelemetry-instrumentation-httpx: support strict typing (#4833)
• opentelemetry-instrumentation-mysqlclient: add semantic convention stability opt-in mode tests (#4834)
• opentelemetry-instrumentation-pymysql: add semantic convention stability opt-in mode tests (#4835)
• opentelemetry-instrumentation-sqlite3: add semantic convention stability opt-in mode tests (#4836)
• opentelemetry-instrumentation-psycopg: add semantic convention stability opt-in mode tests (#4838)
• infra: add validation for changelog file format (#4856)
• opentelemetry-instrumentation-aio-pika: bump maximum admissible aio-pika version to 11.0.0 (#4998)

Changed

• opentelemetry-instrumentation: clarify dependency conflict messages, in logs and in DependencyConflictError, and promote auto-instrumentation version conflict logs to error level (#5025)

Removed

• opentelemetry-instrumentation-kafka-python: drop support for the deprecated kafka-python-ng fork now that kafka-python is actively maintained again (#4839)
• opentelemetry-instrumentation-kafka-python...

  Description has been truncated