Skip to content

fix(deps): allow compatible OpenTelemetry 1.x releases on Python 3.9 - #1458

Open
iuiu-py wants to merge 1 commit into
AgentOps-AI:mainfrom
iuiu-py:fix/opentelemetry-version-ranges
Open

iuiu-py wants to merge 1 commit into
AgentOps-AI:mainfrom
iuiu-py:fix/opentelemetry-version-ranges

Conversation

@iuiu-py

@iuiu-py iuiu-py commented Sep 21, 2026

Copy link
Copy Markdown

Fixes #1246

Why

requires-python still advertises Python 3.9, but the OpenTelemetry dependencies are pinned to 1.29.0 only for Python 3.9. Some compatible AgentOps dependencies require newer OpenTelemetry releases; for example, google-adk==1.5.0 requires opentelemetry-sdk>=1.31.0, so pip reports conflicting requirements instead of resolving a compatible set.

What

Replace the Python-version-specific OpenTelemetry constraints with shared ranges that cover both the existing supported floor and current compatible 1.x releases:

  • opentelemetry-sdk, opentelemetry-api, and opentelemetry-exporter-otlp-proto-http: >=1.29.0,<2.0.0
  • opentelemetry-instrumentation and opentelemetry-semantic-conventions: >=0.50b0,<1.0.0

This keeps the current lower bound while allowing the minor releases already used on newer Python versions.

Testing

  • Parsed pyproject.toml and verified 1.29.0, 1.31.0, and 1.31.1 satisfy the SDK/API/exporter ranges, and 0.50b0/0.52b1 satisfy the instrumentation/semantic-conventions ranges with packaging.
  • Reproduced that the old ==1.29.0 marker rejects opentelemetry-sdk 1.31.0 required by google-adk==1.5.0, while the new range accepts it.
  • uv lock --check was attempted, but PyPI access is unavailable in this environment. The changed lockfile was not regenerated here.

This branch has not been deployed

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Bug]: Dependency on opentelemetry-sdk

1 participant