fix: support opentelemetry-exporter-otlp-proto-http >=1.39.1#4533
fix: support opentelemetry-exporter-otlp-proto-http >=1.39.1#4533hztBUAA wants to merge 1 commit intocrewAIInc:mainfrom
Conversation
The ~=1.34.0 constraint restricted opentelemetry packages to <1.35.0, preventing users from installing opentelemetry-exporter-otlp-proto-http >=1.39.1 needed for Langfuse telemetry integration. Changed from ~=1.34.0 (compatible release, >=1.34.0 <1.35) to >=1.34.0 for opentelemetry-api, opentelemetry-sdk, and opentelemetry-exporter-otlp-proto-http. The OpenTelemetry API is stable post-1.0 and crewAI uses only standard trace/span APIs with no version-specific features. Fixes crewAIInc#4511
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.
This is the final PR Bugbot will review for you during this billing cycle
Your free Bugbot reviews will reset on February 28
Details
Your team is on the Bugbot Free tier. On this plan, Bugbot will review limited PRs each billing cycle for each member of your team.
To receive Bugbot reviews on all of your PRs, visit the Cursor dashboard to activate Pro and start your 14-day free trial.
| "opentelemetry-exporter-otlp-proto-http~=1.34.0", | ||
| "opentelemetry-api>=1.34.0", | ||
| "opentelemetry-sdk>=1.34.0", | ||
| "opentelemetry-exporter-otlp-proto-http>=1.34.0", |
There was a problem hiding this comment.
Missing upper bound on OpenTelemetry version constraints
Low Severity
The three opentelemetry-* constraints were changed to >=1.34.0 with no upper bound, unlike other comparable dependencies in this project (openai>=1.83.0,<3, pyjwt>=2.9.0,<3, litellm>=1.74.9,<3) which all cap at the next major version. If OpenTelemetry ever publishes a 2.x with breaking changes, fresh installs of crewai could resolve to an incompatible version. Using >=1.34.0,<2 would preserve the intended flexibility while protecting against future major-version breaks.
Additional Locations (1)
|
Thanks for the review and feedback. I am following up on this PR now and will either push the requested changes or reply point-by-point shortly. |
|
Quick follow-up: I am reviewing the feedback and will update this PR shortly. |


Summary
Fixes #4511
opentelemetry-api,opentelemetry-sdk, andopentelemetry-exporter-otlp-proto-httpfrom~=1.34.0(which restricts to>=1.34.0, <1.35) to>=1.34.0Test Plan
uv lockresolves successfullytrace,TracerProvider,BatchSpanProcessor,OTLPSpanExporter,Span,Status,StatusCode,Resource,SERVICE_NAME,SpanExportResult) that have not changed between 1.34 and 1.39.1Note
Low Risk
Dependency constraint loosening only; risk is limited to potential incompatibilities with newer OpenTelemetry versions at install/runtime.
Overview
Relaxes version constraints for
opentelemetry-api,opentelemetry-sdk, andopentelemetry-exporter-otlp-proto-httpfrom~=1.34.0to>=1.34.0so newer OpenTelemetry releases can be installed.Updates
uv.lockaccordingly to reflect the broadened dependency range; no runtime code changes are included.Written by Cursor Bugbot for commit 4517b84. This will update automatically on new commits. Configure here.