fix(deps): update third party deps to ~=1.41.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
opentelemetry-api	~=1.39.0 → ~=1.41.0
opentelemetry-exporter-otlp	~=1.39.0 → ~=1.41.0
opentelemetry-sdk	~=1.39.0 → ~=1.41.0

---

Release Notes

open-telemetry/opentelemetry-python (opentelemetry-api)

v1.41.0

Compare Source

• opentelemetry-sdk: Add host resource detector support to declarative file configuration via detection_development.detectors[].host
  (#​5002)
• opentelemetry-sdk: Add container resource detector support to declarative file configuration via detection_development.detectors[].container, using entry point loading of the opentelemetry-resource-detector-containerid contrib package
  (#​5004)
• opentelemetry-sdk: Add create_tracer_provider/configure_tracer_provider to declarative file configuration, enabling TracerProvider instantiation from config files without reading env vars
  (#​4985)
• Enabled the flake8-tidy-import plugins rules for the ruff linter. These rules throw warnings for relative imports in the modules.
  (#​5019)
• opentelemetry-sdk: Fix AttributeError in ExplicitBucketHistogramAggregation when applied to non-Histogram instruments without explicit boundaries
  (#​5034)
• Fix BatchLogRecordProcessor default schedule_delay_millis from 5000ms to 1000ms to comply with the OTel specification. Note: logs may be exported 5x more frequently by default (e.g. for users who don't explicitly set the OTEL_BLRP_SCHEDULE_DELAY env var).
  (#​4998)
• opentelemetry-sdk: Add process resource detector support to declarative file configuration via detection_development.detectors[].process
  (#​5001)
• opentelemetry-sdk: Add shared _parse_headers helper for declarative config OTLP exporters
  (#​5021)
• opentelemetry-api: Replace a broad exception in attribute cleaning tests to satisfy pylint in the lint-opentelemetry-api CI job
• opentelemetry-sdk: Add create_meter_provider/configure_meter_provider to declarative file configuration, enabling MeterProvider instantiation from config files without reading env vars
  (#​4987)
• opentelemetry-sdk: Add create_resource and create_propagator/configure_propagator to declarative file configuration, enabling Resource and propagator instantiation from config files without reading env vars
  (#​4979)
• opentelemetry-sdk: Map Python CRITICAL log level to OTel FATAL severity text per the specification
  (#​4984)
• opentelemetry-sdk: Add file configuration support with YAML/JSON loading, environment variable substitution, and schema validation against the vendored OTel config JSON schema
  (#​4898)
• Fix intermittent CI failures in getting-started and tracecontext jobs caused by GitHub git CDN SHA propagation lag by installing contrib packages from the already-checked-out local copy instead of a second git clone
  (#​4958)
• opentelemetry-sdk: fix type annotations on MetricReader and related types
  (#​4938)
• opentelemetry-sdk: implement log creation metric
  (#​4935)
• opentelemetry-sdk: implement metric reader metrics
  (#​4970)
• opentelemetry-sdk: implement processor metrics
  (#​5012)
• opentelemetry-sdk: upgrade vendored OTel configuration schema from v1.0.0-rc.3 to v1.0.0
  (#​4965)
• improve check-links ci job
  (#​4978)
• Resolve some Pyright type errors in Span/ReadableSpan and utility stubs
  (#​4973)
• opentelemetry-exporter-prometheus: Fix metric name prefix
  (#​4895)
• opentelemetry-api, opentelemetry-sdk: Add deepcopy support for BoundedAttributes and BoundedList
  (#​4934)
• opentelemetry-proto-json, opentelemetry-codegen-json: Implement custom protoc plugin to generate OTLP JSON class definitions
  (#​4910)
• Add configurable max_export_batch_size to OTLP HTTP metrics exporter
  (#​4576)
• opentelemetry-sdk: Implement experimental Meter configurator
  (#​4966)
• opentelemetry-exporter-otlp-proto-http: use consistent protobuf for export request
  (#​5015)
• opentelemetry-sdk: cache TracerConfig into the tracer, this changes an internal interface. Only one Tracer with the same instrumentation scope will be created
  (#​5007)
• Redo OTLPMetricExporter unit tests of max_export_batch_size to use real export
  (#​5036)
• opentelemetry-sdk: Implement experimental Logger configurator
  (#​4980)

v1.40.0

Compare Source

• 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)
• opentelemetry-sdk: automatically generate configuration models using OTel config JSON schema
  (#​4879)

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • "before 9am on monday"
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: uv.lock

Command failed: uv lock --upgrade-package opentelemetry-api --upgrade-package opentelemetry-exporter-otlp --upgrade-package opentelemetry-sdk
Using CPython 3.14.4 interpreter at: /opt/containerbase/tools/python/3.14.4/bin/python3
  × No solution found when resolving dependencies for split (markers:
  │ python_full_version == '3.14.*'):
  ╰─▶ Because mistralai[realtime]==2.1.1 was yanked (reason: This
      version included a broken import: ChatCompletionChoice missing
      from client.models exports) and only the following versions of
      mistralai[realtime] are available:
          mistralai[realtime]<=2.0.0
          mistralai[realtime]==2.0.1
          mistralai[realtime]==2.0.2
          mistralai[realtime]==2.0.3
          mistralai[realtime]==2.0.4
          mistralai[realtime]==2.0.5
          mistralai[realtime]==2.1.0
          mistralai[realtime]==2.1.1
          mistralai[realtime]==2.1.2
          mistralai[realtime]==2.1.3
          mistralai[realtime]==2.2.0
          mistralai[realtime]==2.3.0
          mistralai[realtime]==2.3.1
          mistralai[realtime]==2.3.2
          mistralai[realtime]==2.4.0
          mistralai[realtime]==2.4.1
      we can conclude that mistralai[realtime]>2.1.0,<2.1.2 cannot be used.
      (1)

      Because opentelemetry-semantic-conventions==0.60b1 depends on
      opentelemetry-api==1.39.1 and only the following versions of
      opentelemetry-semantic-conventions are available:
          opentelemetry-semantic-conventions<=0.60b1
          opentelemetry-semantic-conventions>0.61
      we can conclude that opentelemetry-semantic-conventions>=0.60b1,<0.61
      depends on opentelemetry-api==1.39.1.
      And because all of:
          mistralai>=2.0.0,<=2.1.0
          mistralai>=2.1.2
      depend on opentelemetry-semantic-conventions>=0.60b1,<0.61, we can
      conclude that all of:
          mistralai>=2.0.0,<=2.1.0
          mistralai>=2.1.2
      depend on opentelemetry-api==1.39.1.
      And because we know from (1) that mistralai[realtime]>2.1.0,<2.1.2
      cannot be used, we can conclude that mistralai[realtime]>=2.0.0 depends
      on opentelemetry-api==1.39.1.
      And because livekit-plugins-mistralai depends on
      mistralai[realtime]>=2.0.0 and livekit-agents depends
      on opentelemetry-api>=1.41.0, we can conclude that
      livekit-plugins-mistralai and livekit-agents[anam] are incompatible.
      And because your workspace requires livekit-agents[anam] and
      livekit-plugins-mistralai, we can conclude that your workspace's
      requirements are unsatisfiable.

      hint: Pre-releases are available for `mistralai` in the requested
      range (e.g., 2.4.0rc2), but pre-releases weren't enabled (try:
      `--prerelease=allow`)

      hint: `opentelemetry-semantic-conventions`
      was requested with a pre-release marker (e.g.,
      opentelemetry-semantic-conventions>0.60b1,<0.61), but pre-releases
      weren't enabled (try: `--prerelease=allow`)