Support OpenTelemetry 1.43.0

[strickvl]

🔴 Required Information

Is your feature request related to a specific problem?

Yes. google-adk 2.3.0 through 2.5.0 require:

opentelemetry-api>=1.39,<=1.42.1
opentelemetry-sdk>=1.39,<=1.42.1

ZenML 0.96.2 requires opentelemetry-sdk==1.43.0 as part of its coordinated OpenTelemetry update for FastAPI 0.138 support. This leaves no overlapping SDK version, so standard dependency resolution fails for applications that integrate the two projects.

Minimal resolver reproduction:

printf 'zenml[local,server]==0.96.2\ngoogle-adk==2.5.0\n' \
  | uv pip compile - --python-version 3.12

The relevant resolver error is:

Because zenml==0.96.2 depends on opentelemetry-sdk==1.43.0 and
    google-adk==2.5.0 depends on opentelemetry-sdk>=1.39,<=1.42.1,
we can conclude that google-adk==2.5.0 and zenml==0.96.2 are incompatible.

This currently blocks restoring Google ADK support in Kitaru after its ZenML 0.96.2 upgrade: zenml-io/kitaru#586

Describe the Solution You'd Like

Please test and expand ADK's supported OpenTelemetry range by one release, from:

"opentelemetry-api>=1.39,<=1.42.1"
"opentelemetry-sdk>=1.39,<=1.42.1"

to the narrowest compatible expansion:

"opentelemetry-api>=1.39,<=1.43.0"
"opentelemetry-sdk>=1.39,<=1.43.0"

A CI dependency matrix covering both 1.42.1 and 1.43.0 would preserve the existing supported version while validating the newly accepted one. A narrow <=1.43.0 expansion seems preferable to removing the upper bound because ADK uses unstable OpenTelemetry log APIs.

I created an intentionally unsupported throwaway environment to test the combination before requesting the metadata change. It contained:

• Python 3.12.13 on macOS
• google-adk==2.5.0
• zenml==0.96.2
• opentelemetry-api==1.43.0
• opentelemetry-sdk==1.43.0

Results:

• Kitaru's installed real-ADK contract suite: 10 passed
• ADK 2.5 telemetry tests covering functional telemetry, spans, log records, and concurrent telemetry contexts: 187 passed, 1 skipped

The upstream ADK tests run were:

tests/unittests/telemetry/test_functional.py
tests/unittests/telemetry/test_spans.py
tests/unittests/telemetry/test_telemetry_context.py

These passes are evidence for upstream validation, not a suggestion that downstream projects should override ADK's published constraint.

Impact on your work

Kitaru has a Google ADK adapter that wraps real ADK runners, models, and tools for durable execution and replay. The non-overlapping requirement prevents Kitaru from offering its google-adk installation extra after moving to ZenML 0.96.2, even though the adapter and selected ADK telemetry tests pass with SDK 1.43.0.

A compatible ADK release would let Kitaru restore supported packaging, deterministic integration coverage, live-provider coverage, examples, and documentation without forcing an unsupported dependency override.

Willingness to contribute

Yes. I would be happy to contribute a narrow dependency and test-matrix change if the maintainers agree that supporting 1.43.0 is appropriate.

🟡 Recommended Information

Describe Alternatives You've Considered

• Force an unsupported dependency override: rejected because it contradicts ADK's published compatibility contract.
• Downgrade ADK: current ADK 1.x releases also cap OpenTelemetry below 1.43. ADK 1.14.1 has a broad enough range, but it predates ADK 2.0's breaking API/event/session changes and fails two of Kitaru's ten installed integration contracts around tool confirmation and credential requests.
• Separate package or lockfile: does not solve the conflict because ADK and ZenML still load one SDK version in the same Python interpreter.
• Process isolation: technically possible, but would require replacing an in-process adapter with a substantial RPC architecture.
• Change ZenML's OpenTelemetry line: ZenML's 1.43/0.64 update is coordinated with its FastAPI 0.138 support, so expanding ADK's ceiling appears to be the smaller and better-targeted change.

Proposed API / Implementation

No public ADK API change should be required. The proposed implementation is limited to:

1. Expanding the opentelemetry-api and opentelemetry-sdk upper bounds through 1.43.0.
2. Running ADK's telemetry and general unit suites with both the existing 1.42.1 line and the new 1.43.0 line.

Additional Context

Related prior dependency-range issue: #4898

[Varshith-Kali]

Hi, I'd like to pick this up. The reporter already validated that ADK 2.5.0 telemetry tests pass with opentelemetry 1.43.0 — I'll contribute the narrow dependency-range bump (<=1.42.1 → <=1.43.0) in pyproject.toml along with a CI matrix check covering both 1.42.1 and 1.43.0. Will open a PR shortly.