Conversation
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #1246
Why
requires-pythonstill advertises Python 3.9, but the OpenTelemetry dependencies are pinned to1.29.0only for Python 3.9. Some compatible AgentOps dependencies require newer OpenTelemetry releases; for example,google-adk==1.5.0requiresopentelemetry-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, andopentelemetry-exporter-otlp-proto-http:>=1.29.0,<2.0.0opentelemetry-instrumentationandopentelemetry-semantic-conventions:>=0.50b0,<1.0.0This keeps the current lower bound while allowing the minor releases already used on newer Python versions.
Testing
pyproject.tomland verified1.29.0,1.31.0, and1.31.1satisfy the SDK/API/exporter ranges, and0.50b0/0.52b1satisfy the instrumentation/semantic-conventions ranges withpackaging.==1.29.0marker rejectsopentelemetry-sdk 1.31.0required bygoogle-adk==1.5.0, while the new range accepts it.uv lock --checkwas attempted, but PyPI access is unavailable in this environment. The changed lockfile was not regenerated here.