`opentelemetry-api` pinned to exact patch version

[zzstoatzz]

could this be relaxed? afaict its currently a convoluted way to spell an exact pin on 1.37.0

this causes all sorts of downstream issues, happy to elaborate if anyone feels it's necessary

[GWeale]

Hi @zzstoatzz, would >= 1.36, <= 1.39 help your use case.

it was because of unstable _logs and other _ files in opentelelmetry

[adk-bot]

This issue has been automatically marked as stale because it has not had recent activity for 7 days after a maintainer requested clarification. It will be closed if no further activity occurs within 7 days.

[zevisert]

>= 1.36, <= 1.39.1 would help my use case! opentelemetry-semantic-conventions 0.60b1 depends on opentelemetry-api (1.39.1) now.

[zzstoatzz]

yes @GWeale - that does indeed, thanks!

[cristipufu]

@GWeale So google-adk>=1.24.0 itself allows opentelemetry-sdk>=1.36.0,<1.40.0 now, but we still have a conflict that comes from its transitive dependency chain: google-cloud-aiplatform[agent-engines] -> opentelemetry-exporter-gcp-logging==1.11.0a0 -> opentelemetry-sdk<1.39.0

As a workaround, we're using this:

[tool.uv]
# google-adk transitively depends on opentelemetry-exporter-gcp-logging which
# pins opentelemetry-sdk<1.39.0, but uipath-core requires >=1.39.0.
# google-adk itself allows opentelemetry-sdk>=1.36.0,<1.40.0 (since v1.24.0)
# so 1.39.x is compatible. Force the resolution with an override.
override-dependencies = [
    "opentelemetry-sdk>=1.39.0,<1.40.0",
]