Bump opentelemetry-exporter-otlp from 1.39.1 to 1.40.0

[dependabot]

Bumps opentelemetry-exporter-otlp from 1.39.1 to 1.40.0.

Changelog

Sourced from opentelemetry-exporter-otlp's changelog.

Version 1.40.0/0.61b0 (2026-03-04)

• opentelemetry-sdk: deprecate LoggingHandler in favor of opentelemetry-instrumentation-logging, see opentelemetry-instrumentation-logging documentation (#4919)
• opentelemetry-sdk: Clarify log processor error handling expectations in documentation (#4915)
• bump semantic-conventions to v1.40.0 (#4941)
• Add stale PR GitHub Action (#4926)
• opentelemetry-sdk: Drop unused Jaeger exporter environment variables (exporter removed in 1.22.0) (#4918)
• opentelemetry-sdk: Clarify timeout units in environment variable documentation (#4906)
• opentelemetry-exporter-otlp-proto-grpc: Fix re-initialization of gRPC channel on UNAVAILABLE error (#4825)
• opentelemetry-exporter-prometheus: Fix duplicate HELP/TYPE declarations for metrics with different label sets (#4868)
• Allow loading all resource detectors by setting OTEL_EXPERIMENTAL_RESOURCE_DETECTORS to * (#4819)
• opentelemetry-sdk: Fix the type hint of the _metrics_data property to allow None (#4837).
• Regenerate opentelemetry-proto code with v1.9.0 release (#4840)
• Add python 3.14 support (#4798)
• Silence events API warnings for internal users (#4847)
• opentelemetry-sdk: make it possible to override the default processors in the SDK configurator (#4806)
• Prevent possible endless recursion from happening in SimpleLogRecordProcessor.on_emit, (#4799) and (#4867).
• Implement span start/end metrics (#4880)
• Add environment variable carriers to API (#4609)
• Add experimental composable rule based sampler (#4882)
• Make ConcurrentMultiSpanProcessor fork safe (#4862)
• opentelemetry-exporter-otlp-proto-http: fix retry logic and error handling for connection failures in trace, metric, and log exporters (#4709)
• opentelemetry-sdk: avoid RuntimeError during iteration of view instrument match dictionary in MetricReaderStorage.collect() (#4891)
• Implement experimental TracerConfigurator (#4861)
• opentelemetry-sdk: Fix instrument creation race condition (#4913)
• bump semantic-conventions to v1.39.0 (#4914)

... (truncated)

Commits

• dd22021 Prepare release 1.40.0/0.61b0 (#4949)
• 26c7166 api: add docstrings to core metrics instrument abstract methods (#4923)
• c17ba89 opentelemetry-sdk: deprecate logging handler (#4919)
• 6ea15ff docs: Clarify log processor error handling expectations (#4915)
• 24f4fb0 bump semconv to v1.40.0 (#4941)
• 2308baf maint: Add stale github action (#4926)
• 99b47df config: generate model code from json schema (#4879)
• 9a658ac Add Lukas to approvers (#4939)
• 1c64c14 opentelemetry-sdk: change sdk metrics related parameters as named (#4937)
• 7247af7 opentelemetry-sdk: change sdk metrics related parameters as named (#4937)
• Additional commits viewable in compare view

You can trigger a rebase of this PR by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

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

[github-actions]

CI Commands

The following CI workflows run automatically on every push and pull request:

Workflow	What it runs
GPU Cluster Monitoring Python CI	lint, tests, typecheck, format, deb build, pyoxidizer builds
Go packages CI	shelper tests, format, lint

---

The following commands can be used by maintainers to trigger additional tests that require access to secrets:

Command	Description	Requires approval?
/metaci tests	Runs Meta internal integration tests (pytest)	Yes — a maintainer must trigger the command and approve the deployment request
/metaci integration tests	Same as above (alias)	Yes

Note: Only repository maintainers (OWNER association) can trigger /metaci commands. After commenting the command, a maintainer must also navigate to the Actions tab and approve the deployment to the graph-api-access environment before the jobs will run. See the approval guidelines for what to approve or reject.