Skip to content

Update opentelemetry-api and opentelemetry-sdk to < 2 (Updated) #7433

Description

@BrownMunda1

Wanted to propose an update in the core OTel libraries in the dependencies section of pyproject.toml

opentelemetry-api<=1.42.1 —> opentelemetry-api<2 (

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

opentelemetry-sdk<=1.42.1 —> opentelemetry-sdk<2 (

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

If not possible, would love to know why are the version bumps not possible, where is the exact point which would break if the OTel versions are updated

Thanks

Activity

  1. reddynitish commented on Oct 7, 2026

    @reddynitish
    Contributor

    I’m interested in investigating this compatibility update, if nobody has already started. Current main still caps opentelemetry-api and opentelemetry-sdk at 1.42.1. I would first check dependency resolution with the telemetry extras/exporters and run the relevant telemetry tests against 1.44.0. If compatible, I would propose the smallest constraint update with validation evidence; if there is a real blocker, I would document it here rather than blindly raise the bounds.

    I found no public claim or matching PR for this issue. If the author or another contributor already has work underway, please let me know so I can avoid duplication. Maintainers: is investigating this bump welcome, or are these upper bounds intentional?

    I plan to use Codex assistance. This is an interest/coordination request; I’m prioritizing one contribution at a time rather than promising simultaneous delivery.

  2. self-assigned this
    on Oct 8, 2026
  3. reddynitish commented on Oct 8, 2026

    @reddynitish
    Contributor

    I am starting the compatibility investigation now, using Codex assistance. I will reproduce the current install restriction with OpenTelemetry 1.44.0, check dependency resolution for the telemetry extras, and run the telemetry tests against the proposed bounds. If those checks pass, I will submit a minimal dependency update with the validation results. I checked the issue timeline and open PRs again and found no public competing implementation; please let me know if work is already underway privately.

  4. added
    core[Component] This issue is related to the core interface and implementation
    tracing[Component] This issue is related to OpenTelemetry tracing
    and removed
    core[Component] This issue is related to the core interface and implementation
    on Oct 9, 2026
  5. added theissue type on Oct 9, 2026
  6. llalitkumarrr commented on Oct 9, 2026

    @llalitkumarrr
    Collaborator

    Hello @BrownMunda1,

    Thank you for raising this. Could you provide some context regarding this request? Specifically are you encountering a dependency conflict with another package that requires a newer OpenTelemetry version or is there a particular feature or fix in version 1.44.0 that you require? If you are facing a conflict please share the package name and the associated error message.

  7. added
    request clarification[Status] The maintainer need clarification or more information from the author
    on Oct 9, 2026
  8. BrownMunda1 commented on Oct 9, 2026

    @BrownMunda1
    Author

    @llalitkumarrr we're aiming to make use of splunk-opentelemetry for tracing. splunk-opentelemetry's version 2.12.1 is dependent on OTel 1.44.0. We just want to be able to make use of that latest version along with google-adk's latest version. If there is something for which google-adk has a hard dependency on OTel <=1.42.1, would love to know that

  9. BrownMunda1 commented on Oct 18, 2026

    @BrownMunda1
    Author

    @llalitkumarrr @jawoszek Please have a look at the PR shared by @krisztianfekete, can we do it in a similar way for google-adk as well? Seems to be not breaking/blocking anything as per the PR raised by @reddynitish

    Idea is to not be limited to 1.42.1

  10. rcleveng commented on Oct 25, 2026

    @rcleveng

    Actually can we go up to 1.45.1, this is holding back langfuse for me on v4 python SDK.

  11. changed the title [-]Update opentelemetry-api and opentelemetry-sdk to 1.44.0[/-] [+]Update opentelemetry-api and opentelemetry-sdk to < 2 (Updated)[/+] on Oct 26, 2026
  12. adk-bot commented on Oct 27, 2026

    @adk-bot
    Collaborator

    Notification: The author has updated the issue description. Maintainers, please review.

  13. ljfraney commented on Oct 27, 2026

    @ljfraney

    Actually can we go up to 1.45.1, this is holding back langfuse for me on v4 python SDK.

    Second this. Version 1.45.1 is currently the only version available that is not affected by CVE-2026-114603.

  14. osttra-dag-lovenvald commented on Oct 30, 2026

    @osttra-dag-lovenvald

    9. Hello @BrownMunda1,
    Thank you for raising this. Could you provide some context regarding this request? Specifically are you encountering a dependency conflict with another package that requires a newer OpenTelemetry version or is there a particular feature or fix in version 1.44.0 that you require? If you are facing a conflict please share the package name and the associated error message.

    This creates a dependency conflict with FastAPI:

    1. google-adk==2.13.0 places a strict upper bound on OpenTelemetry:
      opentelemetry-api ≤ 1.42.1 and opentelemetry-sdk ≤ 1.42.1
      2. fastapi[standard]==0.162.0 (starting in FastAPI ≥ 0.142.0) adds built-in telemetry requiring:
      opentelemetry-exporter-otlp-proto-http ≥ 1.44.0 and opentelemetry-api ≥ 1.44.0
      3. Because google-adk caps OpenTelemetry at 1.42.1 and fastapi[standard] requires at least 1.44.0, they cannot coexist.
  15. BrownMunda1 commented on Oct 31, 2026

    @BrownMunda1
    Author

    Have created a PR which addresses the issues above by bumping up to the latest otel versions available: #7756
    @llalitkumarrr Please have a look!

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

Metadata

Metadata

Assignees

Labels

request clarification[Status] The maintainer need clarification or more information from the authortracing[Component] This issue is related to OpenTelemetry tracing

Type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions