Bump the rust group across 1 directory with 7 updates

[dependabot]

Bumps the rust group with 7 updates in the / directory:

Package	From	To
pyo3	0.29.2	0.29.3
opentelemetry	0.32.0	0.33.0
opentelemetry-otlp	0.32.0	0.33.0
opentelemetry-stdout	0.32.0	0.33.0
opentelemetry_sdk	0.32.1	0.33.0
tracing-opentelemetry	0.33.0	0.34.0
uuid	1.26.1	1.27.0

Updates pyo3 from 0.29.2 to 0.29.3

Release notes

Sourced from pyo3's releases.

PyO3 0.29.3

This release is a series of fixes worth landing to the PyO3 0.29 series; the PyO3 0.30 release is planned to follow within a few weeks, however during the development cycle a number of rough edges were discovered which were deemed worth a backport.

The patch broadly includes:

• a further fix the to the opt-out of raw-dylib linking for Windows introduced in PyO3 0.29.1 (the switch to raw-dylib linking was introduced in PyO3 0.29.0),
• fixes to support GraalPy on windows,
• a handful of small performance optimizations,
• a number of non-breaking fixes to the experimental-inspect type stub generation (expect more improvements in 0.30), and
• various other bugfixes such as to FFI definitions, to resolve crashes, and to fix clippy lints caused by PyO3 macros.

For a full list of the exact fixes please consult the CHANGELOG.

Thank you to the following contributors for the improvements:

@​adamgerhant-ai @​alex @​bschoenmaeckers @​charliermarsh @​chirizxc @​davidhewitt @​dependabot[bot] @​dylanpulver @​exg @​FranciscoTGouveia @​JMak-Security @​jonasdedden @​jorenham @​konstin @​latent-9 @​mejrs @​ngoldbaum @​Person-93 @​PeterFaiman @​sneakers-the-rat

Changelog

Sourced from pyo3's changelog.

[0.29.3] - 2026-09-30

Packaging

• Support GraalPy on Windows. #6406

Added

• Add FFI definitions PyModule_GetState_DuringGC, PyModule_GetToken_DuringGC, PyObject_GetTypeData_DuringGC, PyType_GetModuleState_DuringGC, PyType_GetBaseByToken_DuringGC, PyType_GetModule_DuringGC, and PyType_GetModuleByToken_DuringGC for Python 3.15 and up. #6419

Changed

• Optimize u128/i128 conversions on Python 3.15+. #6160
• Preallocate output sets when extracting Python set and frozenset values into Rust hash sets. #6225
• Optimize PyBytes::as_bytes() when not using abi3 or abi3t. #6377

Removed

• Remove FFI definitions PyExc_RecursionErrorInst and Py_UseClassExceptionsFlag (not present in supported Python versions). #6421

Fixed

• Revert removal of FFI definition _PyFrameEvalFunction, _PyInterpreterState_GetEvalFrameFunc and _PyInterpreterState_SetEvalFrameFunc, which are not currently treated as CPython private API despite their name. #6195
• Fix FFI definition PyUnstable_Eval_RequestCodeExtraIndex FFI binding to link to the private CPython symbol on Python versions before 3.12. #6195
• Fix FFI definitions PyByteArray_GET_SIZE, PyList_GET_SIZE, and PySet_GET_SIZE to use an atomic load for free-threaded Python. #6230
• experimental-inspect: deduplicate repeated members of a type union in the generated stubs, and put a space on both sides of the | rather than only before it. #6273
• experimental-inspect: __next__ and __anext__ returning Option<T> (or PyResult<Option<T>>) are now introspected as returning T, since None stops the iteration instead of being yielded. #6274
• Fix clippy::clone_on_copy warnings triggered on nightly Rust by #[pyclass(from_py_object)] on classes which implement Copy. #6309
• experimental-inspect: __pow__, __rpow__ and __get__ now introspect their trailing argument as defaulting to None, matching the CPython slot wrappers which substitute None when it is omitted. #6363
• experimental-inspect: fix the stubs of a package nested inside another package being written into a directory named after its parent instead of its own name. #6365
• Fix many unresolved symbols when linking for PyPy due to incorrect link names in pyo3-ffi. #6389
• Fix empty tuple type hints being rendered as invalid tuple[] instead of tuple[()] in generated stubs and PyStaticExpr display. #6393
• experimental-inspect: escape stub docstrings to prevent invalid Python syntax. #6394
• experimental-inspect: fix the generated type annotation for PyBuffer on python <3.12 by using typing_extensions.Buffer instead of collections.abc.Buffer. #6395
• Fix string constants containing control characters rendering as invalid Python in Display for PyStaticExpr. #6397
• Fix crash when a detached thread is terminated while trying to reattach during interpreter finalization. #6404
• Fix link failures on 32-bit Windows when raw-dylib linking is disabled. #6410
• Fix DLL load failures on Windows with PyPy when raw-dylib linking is disabled. #6410
• Fix FFI definition PyVectorcall_Call failing to link on Python 3.11 and older. #6410
• Fix many unresolved data symbols when linking for PyPy due to incorrect link names in pyo3-ffi. #6421
• Fix linker errors on PyPy for outdated FFI definitions where PyPy moved from a function to a macro. #6422
• Fix crash when GC traverses a #[pyclass] type object during class attribute initialization. #6453

Commits

• 451d99f release: 0.29.3
• a19b491 ci: Exclude the Python extensions article from guide checks (#6472)
• d76560a ci: exclude current release tag from link check (#6463)
• 91c0e7d fix crash with GC during attribute initialization (#6453)
• 9d467b1 only override env vars on Python 3.8
• 945e62a bump GraalPy versions tested in CI, test graalpy on windows (#6406)
• 9712753 fix 3.8 ffi checks
• 42a8fcc fix clippy lint (#6334)
• 018dbcc Add DuringGC FFI bindings for 3.15 (#6419)
• 75ada93 fix FFI cases where PyPy replaced function with macro (#6422)
• Additional commits viewable in compare view

Updates opentelemetry from 0.32.0 to 0.33.0

Release notes

Sourced from opentelemetry's releases.

0.33.0

See the 0.33.0 release notes and migration guidance.

The OTLP exporters for Logs and Metrics remain release candidates. We plan to declare them stable in 0.33.1 after approximately two weeks of validation, provided no issues requiring breaking API changes arise. The Logs and Metrics API and SDK remain stable; Distributed Tracing remains pre-stable.

opentelemetry-semantic-conventions-0.32.1

See the CHANGELOG for details.

Changelog

Sourced from opentelemetry's changelog.

Release Notes 0.33

The OTLP exporters for Logs and Metrics remain in release-candidate (RC) status in OpenTelemetry Rust 0.33.0. We intend to declare them stable in 0.33.1, approximately two weeks after this release, provided the RC period does not uncover any issues requiring breaking API changes. During this period, we expect only compatible fixes, documentation updates, and low-risk internal optimisations.

OpenTelemetry Rust 0.33.0 brings OTLP retries on by default and completes the stabilisation cleanups that began in 0.32. The Logs and Metrics API and SDK remain stable with no breaking changes. The Distributed Tracing API, SDK, and OTLP exporter remain pre-stable, and this release includes intentional breaking changes in that area to continue preparing it for stabilisation.

For detailed changelogs of individual crates, refer to their respective changelog files. This document summarises the key changes.

Key Changes

OTLP Exporters for Logs and Metrics (RC)

Version 0.33.0 keeps the OTLP exporters for Logs and Metrics in RC for a final validation period. If no issues requiring breaking API changes are identified, we intend to declare them stable in 0.33.1 approximately two weeks after this release.

Retries enabled by default

OTLP/HTTP and OTLP/gRPC retries are now enabled by default with exponential backoff, jitter, and up to 3 retries (4 attempts total). Use .with_retry_policy(RetryPolicy::disabled()) to opt out, or provide a custom RetryPolicy.

Users of the experimental retry feature flags (experimental-grpc-retry and experimental-http-retry) should remove them from Cargo.toml. The retry and retry_classification modules are now crate-private; replace opentelemetry_otlp::retry imports with opentelemetry_otlp::RetryPolicy and use its with_* methods instead of struct literals.

Stabilisation cleanups

• Breaking for callers matching or constructing removed build-error variants: ExporterBuildError now has two exhaustive variants, InvalidConfiguration(String) and InternalFailure(String). Update uses of removed variants. Normal exporter builder calls and propagation of build errors with ? need no changes. See the OTLP changelog for migration examples.
• Breaking Protocol and Compression are now #[non_exhaustive]. Exhaustive matches must add a wildcard arm.
• Breaking Protocol::from_env() is now crate-private. Builders resolve OTEL_EXPORTER_OTLP_PROTOCOL automatically; read the env var directly if needed.
• Invalid OTLP endpoint environment variables (HTTP and gRPC) now produce a

... (truncated)

Commits

• 1983384 docs: clarify OTLP 0.33 migration guidance (#3747)
• dacfeda chore: Prepare for release v0.33.0 (RC) (#3712)
• 996ac1e refactor(http)!: make ResponseBodyTooLarge extensible (#3736)
• d328c65 fix(proto): preserve scope metadata when grouping OTLP logs (#3740)
• e652efd refactor(otlp): finalize exporter build error API (#3692)
• 8809c42 refactor(otlp)!: separate configuration parsing errors (#3742)
• cc1c374 feat(otlp): Allow to provide http client wrapped in Arc for user (#3468)
• e085c61 ci: use supported Debian image for benchmarks (#3744)
• 6c5fd58 fix(proto): accept omitted partial success fields (#3739)
• 51b36a7 fix(otlp): handle enum environment values consistently (#3730)
• Additional commits viewable in compare view

Updates opentelemetry-otlp from 0.32.0 to 0.33.0

Changelog

Sourced from opentelemetry-otlp's changelog.

Release Notes 0.33

The OTLP exporters for Logs and Metrics remain in release-candidate (RC) status in OpenTelemetry Rust 0.33.0. We intend to declare them stable in 0.33.1, approximately two weeks after this release, provided the RC period does not uncover any issues requiring breaking API changes. During this period, we expect only compatible fixes, documentation updates, and low-risk internal optimisations.

OpenTelemetry Rust 0.33.0 brings OTLP retries on by default and completes the stabilisation cleanups that began in 0.32. The Logs and Metrics API and SDK remain stable with no breaking changes. The Distributed Tracing API, SDK, and OTLP exporter remain pre-stable, and this release includes intentional breaking changes in that area to continue preparing it for stabilisation.

For detailed changelogs of individual crates, refer to their respective changelog files. This document summarises the key changes.

Key Changes

OTLP Exporters for Logs and Metrics (RC)

Version 0.33.0 keeps the OTLP exporters for Logs and Metrics in RC for a final validation period. If no issues requiring breaking API changes are identified, we intend to declare them stable in 0.33.1 approximately two weeks after this release.

Retries enabled by default

OTLP/HTTP and OTLP/gRPC retries are now enabled by default with exponential backoff, jitter, and up to 3 retries (4 attempts total). Use .with_retry_policy(RetryPolicy::disabled()) to opt out, or provide a custom RetryPolicy.

Users of the experimental retry feature flags (experimental-grpc-retry and experimental-http-retry) should remove them from Cargo.toml. The retry and retry_classification modules are now crate-private; replace opentelemetry_otlp::retry imports with opentelemetry_otlp::RetryPolicy and use its with_* methods instead of struct literals.

Stabilisation cleanups

• Breaking for callers matching or constructing removed build-error variants: ExporterBuildError now has two exhaustive variants, InvalidConfiguration(String) and InternalFailure(String). Update uses of removed variants. Normal exporter builder calls and propagation of build errors with ? need no changes. See the OTLP changelog for migration examples.
• Breaking Protocol and Compression are now #[non_exhaustive]. Exhaustive matches must add a wildcard arm.
• Breaking Protocol::from_env() is now crate-private. Builders resolve OTEL_EXPORTER_OTLP_PROTOCOL automatically; read the env var directly if needed.
• Invalid OTLP endpoint environment variables (HTTP and gRPC) now produce a

... (truncated)

Commits

• 1983384 docs: clarify OTLP 0.33 migration guidance (#3747)
• dacfeda chore: Prepare for release v0.33.0 (RC) (#3712)
• 996ac1e refactor(http)!: make ResponseBodyTooLarge extensible (#3736)
• d328c65 fix(proto): preserve scope metadata when grouping OTLP logs (#3740)
• e652efd refactor(otlp): finalize exporter build error API (#3692)
• 8809c42 refactor(otlp)!: separate configuration parsing errors (#3742)
• cc1c374 feat(otlp): Allow to provide http client wrapped in Arc for user (#3468)
• e085c61 ci: use supported Debian image for benchmarks (#3744)
• 6c5fd58 fix(proto): accept omitted partial success fields (#3739)
• 51b36a7 fix(otlp): handle enum environment values consistently (#3730)
• Additional commits viewable in compare view

Updates opentelemetry-stdout from 0.32.0 to 0.33.0

Release notes

Sourced from opentelemetry-stdout's releases.

0.33.0

See the 0.33.0 release notes and migration guidance.

The OTLP exporters for Logs and Metrics remain release candidates. We plan to declare them stable in 0.33.1 after approximately two weeks of validation, provided no issues requiring breaking API changes arise. The Logs and Metrics API and SDK remain stable; Distributed Tracing remains pre-stable.

opentelemetry-semantic-conventions-0.32.1

See the CHANGELOG for details.

Changelog

Sourced from opentelemetry-stdout's changelog.

Release Notes 0.33

The OTLP exporters for Logs and Metrics remain in release-candidate (RC) status in OpenTelemetry Rust 0.33.0. We intend to declare them stable in 0.33.1, approximately two weeks after this release, provided the RC period does not uncover any issues requiring breaking API changes. During this period, we expect only compatible fixes, documentation updates, and low-risk internal optimisations.

OpenTelemetry Rust 0.33.0 brings OTLP retries on by default and completes the stabilisation cleanups that began in 0.32. The Logs and Metrics API and SDK remain stable with no breaking changes. The Distributed Tracing API, SDK, and OTLP exporter remain pre-stable, and this release includes intentional breaking changes in that area to continue preparing it for stabilisation.

For detailed changelogs of individual crates, refer to their respective changelog files. This document summarises the key changes.

Key Changes

OTLP Exporters for Logs and Metrics (RC)

Version 0.33.0 keeps the OTLP exporters for Logs and Metrics in RC for a final validation period. If no issues requiring breaking API changes are identified, we intend to declare them stable in 0.33.1 approximately two weeks after this release.

Retries enabled by default

OTLP/HTTP and OTLP/gRPC retries are now enabled by default with exponential backoff, jitter, and up to 3 retries (4 attempts total). Use .with_retry_policy(RetryPolicy::disabled()) to opt out, or provide a custom RetryPolicy.

Users of the experimental retry feature flags (experimental-grpc-retry and experimental-http-retry) should remove them from Cargo.toml. The retry and retry_classification modules are now crate-private; replace opentelemetry_otlp::retry imports with opentelemetry_otlp::RetryPolicy and use its with_* methods instead of struct literals.

Stabilisation cleanups

• Breaking for callers matching or constructing removed build-error variants: ExporterBuildError now has two exhaustive variants, InvalidConfiguration(String) and InternalFailure(String). Update uses of removed variants. Normal exporter builder calls and propagation of build errors with ? need no changes. See the OTLP changelog for migration examples.
• Breaking Protocol and Compression are now #[non_exhaustive]. Exhaustive matches must add a wildcard arm.
• Breaking Protocol::from_env() is now crate-private. Builders resolve OTEL_EXPORTER_OTLP_PROTOCOL automatically; read the env var directly if needed.
• Invalid OTLP endpoint environment variables (HTTP and gRPC) now produce a

... (truncated)

Commits

• 1983384 docs: clarify OTLP 0.33 migration guidance (#3747)
• dacfeda chore: Prepare for release v0.33.0 (RC) (#3712)
• 996ac1e refactor(http)!: make ResponseBodyTooLarge extensible (#3736)
• d328c65 fix(proto): preserve scope metadata when grouping OTLP logs (#3740)
• e652efd refactor(otlp): finalize exporter build error API (#3692)
• 8809c42 refactor(otlp)!: separate configuration parsing errors (#3742)
• cc1c374 feat(otlp): Allow to provide http client wrapped in Arc for user (#3468)
• e085c61 ci: use supported Debian image for benchmarks (#3744)
• 6c5fd58 fix(proto): accept omitted partial success fields (#3739)
• 51b36a7 fix(otlp): handle enum environment values consistently (#3730)
• Additional commits viewable in compare view

Updates opentelemetry_sdk from 0.32.1 to 0.33.0

Changelog

Sourced from opentelemetry_sdk's changelog.

Release Notes 0.33

The OTLP exporters for Logs and Metrics remain in release-candidate (RC) status in OpenTelemetry Rust 0.33.0. We intend to declare them stable in 0.33.1, approximately two weeks after this release, provided the RC period does not uncover any issues requiring breaking API changes. During this period, we expect only compatible fixes, documentation updates, and low-risk internal optimisations.

OpenTelemetry Rust 0.33.0 brings OTLP retries on by default and completes the stabilisation cleanups that began in 0.32. The Logs and Metrics API and SDK remain stable with no breaking changes. The Distributed Tracing API, SDK, and OTLP exporter remain pre-stable, and this release includes intentional breaking changes in that area to continue preparing it for stabilisation.

For detailed changelogs of individual crates, refer to their respective changelog files. This document summarises the key changes.

Key Changes

OTLP Exporters for Logs and Metrics (RC)

Version 0.33.0 keeps the OTLP exporters for Logs and Metrics in RC for a final validation period. If no issues requiring breaking API changes are identified, we intend to declare them stable in 0.33.1 approximately two weeks after this release.

Retries enabled by default

OTLP/HTTP and OTLP/gRPC retries are now enabled by default with exponential backoff, jitter, and up to 3 retries (4 attempts total). Use .with_retry_policy(RetryPolicy::disabled()) to opt out, or provide a custom RetryPolicy.

Users of the experimental retry feature flags (experimental-grpc-retry and experimental-http-retry) should remove them from Cargo.toml. The retry and retry_classification modules are now crate-private; replace opentelemetry_otlp::retry imports with opentelemetry_otlp::RetryPolicy and use its with_* methods instead of struct literals.

Stabilisation cleanups

• Breaking for callers matching or constructing removed build-error variants: ExporterBuildError now has two exhaustive variants, InvalidConfiguration(String) and InternalFailure(String). Update uses of removed variants. Normal exporter builder calls and propagation of build errors with ? need no changes. See the OTLP changelog for migration examples.
• Breaking Protocol and Compression are now #[non_exhaustive]. Exhaustive matches must add a wildcard arm.
• Breaking Protocol::from_env() is now crate-private. Builders resolve OTEL_EXPORTER_OTLP_PROTOCOL automatically; read the env var directly if needed.
• Invalid OTLP endpoint environment variables (HTTP and gRPC) now produce a

... (truncated)

Commits

• 1983384 docs: clarify OTLP 0.33 migration guidance (#3747)
• dacfeda chore: Prepare for release v0.33.0 (RC) (#3712)
• 996ac1e refactor(http)!: make ResponseBodyTooLarge extensible (#3736)
• d328c65 fix(proto): preserve scope metadata when grouping OTLP logs (#3740)
• e652efd refactor(otlp): finalize exporter build error API (#3692)
• 8809c42 refactor(otlp)!: separate configuration parsing errors (#3742)
• cc1c374 feat(otlp): Allow to provide http client wrapped in Arc for user (#3468)
• e085c61 ci: use supported Debian image for benchmarks (#3744)
• 6c5fd58 fix(proto): accept omitted partial success fields (#3739)
• 51b36a7 fix(otlp): handle enum environment values consistently (#3730)
• Additional commits viewable in compare view

Updates tracing-opentelemetry from 0.33.0 to 0.34.0

Changelog

Sourced from tracing-opentelemetry's changelog.

0.34.0 - 2026-09-20

Other

• Upgrade to OpenTelemetry 0.33, see upstream changelog for details (#268)

Commits

• See full diff in compare view

Updates uuid from 1.26.1 to 1.27.0

Release notes

Sourced from uuid's releases.

v1.27.0

What's Changed

• Accept case-insensitive urn:uuid: prefixes when parsing by @​jaideeppyne in uuid-rs/uuid#912
• Fix ordering of V7 UUIDs created by earlier seconds with later subsec nanos by @​KodrAus in uuid-rs/uuid#915
• Prepare for 1.27.0 release by @​KodrAus in uuid-rs/uuid#917

New Contributors

• @​jaideeppyne made their first contribution in uuid-rs/uuid#912

Full Changelog: uuid-rs/uuid@v1.26.1...v1.27.0

Commits

• b62154e Merge pull request #917 from uuid-rs/cargo/v1.27.0
• ffd8ec5 prepare for 1.27.0 release
• 4b6c10f Merge pull request #915 from uuid-rs/fix/v7-ordering
• a1aa126 Merge pull request #912 from jaideeppyne/fix/urn-prefix-case-insensitive
• 4639d67 fix ordering of V7 UUIDs created by earlier seconds with later subsec nanos
• 2723703 bump MSRV to 1.89.0
• a3e64fa refactor: simplify URN prefix parsing
• 5055fd4 refactor: inline case-insensitive URN prefix checks
• cb8b1d5 refactor: simplify case-insensitive URN parsing
• 285967d Accept case-insensitive urn:uuid: prefixes when parsing
• See full diff in compare view

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

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

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

[codspeed]

Merging this PR will not alter performance

✅ 14 untouched benchmarks

---

_{Comparing dependabot/cargo/rust-a1a155fab8 (cf2e76b) with main (22bfc5a)}