Skip to content

fix: support OpenTelemetry 1.39+ by relaxing version constraints#4913

Open
brucearctor wants to merge 2 commits intogoogle:mainfrom
brucearctor:fix/support-opentelemetry-1.39
Open

fix: support OpenTelemetry 1.39+ by relaxing version constraints#4913
brucearctor wants to merge 2 commits intogoogle:mainfrom
brucearctor:fix/support-opentelemetry-1.39

Conversation

@brucearctor
Copy link
Copy Markdown

Link to Issue or Description of Change

1. Link to an existing issue:

Description

The <1.39.0 upper bound on opentelemetry-api and opentelemetry-sdk was added due to agent_engines exporter constraints in google-cloud-aiplatform. The upstream package (latest v1.141.0) now specifies opentelemetry-sdk<2 for both the agent-engines and reasoningengine extras, so this constraint is no longer needed.

Changes:

  • opentelemetry-api>=1.36.0, <1.39.0opentelemetry-api>=1.36.0, <2.0.0
  • opentelemetry-sdk>=1.36.0, <1.39.0opentelemetry-sdk>=1.36.0, <2.0.0

Testing Plan

Unit Tests:

  • No new unit tests needed — this is a dependency version constraint change only.
  • All unit tests pass locally.
5010 passed, 1943 warnings, 6 subtests passed in 78.64s

Manual End-to-End (E2E) Tests:

N/A — no code changes, only dependency metadata.

Checklist

  • I have read the CONTRIBUTING.md document.
  • I have performed a self-review of my own code.
  • I have commented my code, particularly in hard-to-understand areas.
  • New and existing unit tests pass locally with my changes.
  • Any dependent changes have been merged and published in downstream modules.

Additional context

Verified on PyPI that google-cloud-aiplatform==1.141.0 specifies opentelemetry-sdk<2 for agent-engines extra, confirming the upstream constraint has been relaxed.

@adk-bot adk-bot added the tracing [Component] This issue is related to OpenTelemetry tracing label Mar 20, 2026
@rohityan rohityan self-assigned this Mar 20, 2026
@rohityan rohityan added the needs review [Status] The PR/issue is awaiting review from the maintainer label Mar 20, 2026
@rohityan
Copy link
Copy Markdown
Collaborator

Hi @brucearctor, Thank you for your contribution! We appreciate you taking the time to submit this pull request. Your PR has been received by the team and is currently under review. We will provide feedback as soon as we have an update to share.

@rohityan
Copy link
Copy Markdown
Collaborator

Hi @Jacksunwei , can you please review this.

@RoniFinTech4
Copy link
Copy Markdown

hi, what's the latest here?

@partha-lgtm
Copy link
Copy Markdown

google-adk 1.15+ transitively pulls opentelemetry-exporter-gcp-logging (via google-cloud-aiplatform[agent-engines]), and THAT package also caps OTel <1.39.0. Is there any work on that side @rohityan

The <1.39.0 upper bound on opentelemetry-api and opentelemetry-sdk was
added due to agent_engines exporter constraints in
google-cloud-aiplatform. The upstream package (v1.141.0) now allows
opentelemetry-sdk<2, so this constraint is no longer needed.

The opentelemetry-exporter-gcp-logging package was also updated upstream
(1.10.0a0+) to require opentelemetry-sdk>=1.39.0, confirming the
ecosystem has moved past the old cap.

Relaxes both opentelemetry-api and opentelemetry-sdk to <2.0.0.

Fixes google#4898
@brucearctor brucearctor force-pushed the fix/support-opentelemetry-1.39 branch from 5aea40f to c8d0aae Compare April 23, 2026 23:44
@brucearctor
Copy link
Copy Markdown
Author

@partha-lgtm It looks like that concern has actually already been addressed upstream. The opentelemetry-exporter-gcp-logging package was updated in GoogleCloudPlatform/opentelemetry-operations-python#461 — versions 1.10.0a0+ now require opentelemetry-sdk >= 1.39.0 (flipping the old < 1.39.0 cap). You can see the current constraint in setup.cfg.

So once this PR's OTel relaxation to < 2.0.0 lands, pip will resolve to opentelemetry-exporter-gcp-logging >= 1.10.0a0 alongside OTel 1.39+. No additional changes needed on the transitive side, unless I am missing something?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

needs review [Status] The PR/issue is awaiting review from the maintainer tracing [Component] This issue is related to OpenTelemetry tracing

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Support OpenTelemetry 1.39

5 participants