Skip to content

fix: support opentelemetry-exporter-otlp-proto-http >=1.39.1#4533

Open
hztBUAA wants to merge 1 commit intocrewAIInc:mainfrom
hztBUAA:fix/relax-otel-version-constraint
Open

fix: support opentelemetry-exporter-otlp-proto-http >=1.39.1#4533
hztBUAA wants to merge 1 commit intocrewAIInc:mainfrom
hztBUAA:fix/relax-otel-version-constraint

Conversation

@hztBUAA
Copy link

@hztBUAA hztBUAA commented Feb 20, 2026

Summary

Fixes #4511

  • Relaxed version constraints for opentelemetry-api, opentelemetry-sdk, and opentelemetry-exporter-otlp-proto-http from ~=1.34.0 (which restricts to >=1.34.0, <1.35) to >=1.34.0
  • This allows users to install newer OpenTelemetry versions (e.g., 1.39.1) needed for proper telemetry export to Langfuse and other OTLP collectors
  • The OpenTelemetry API is stable post-1.0 and crewAI uses only standard trace/span/exporter APIs with no version-specific features, so newer versions are fully compatible

Test Plan

  • All 28 telemetry tests pass with the relaxed constraints
  • uv lock resolves successfully
  • Verified crewAI only uses stable OpenTelemetry APIs (trace, TracerProvider, BatchSpanProcessor, OTLPSpanExporter, Span, Status, StatusCode, Resource, SERVICE_NAME, SpanExportResult) that have not changed between 1.34 and 1.39.1

Note

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, and opentelemetry-exporter-otlp-proto-http from ~=1.34.0 to >=1.34.0 so newer OpenTelemetry releases can be installed.

Updates uv.lock accordingly 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.

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
@chatgpt-codex-connector
Copy link

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

Copy link

@cursor cursor bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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",
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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)

Fix in Cursor Fix in Web

@hztBUAA
Copy link
Author

hztBUAA commented Feb 25, 2026

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.

@hztBUAA
Copy link
Author

hztBUAA commented Feb 25, 2026

Quick follow-up: I am reviewing the feedback and will update this PR shortly.

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] Supporting opentelemetry-exporter-otlp-proto-http>=1.39.1

1 participant