crewai - ✅(Solved) Fix [BUG] Supporting opentelemetry-exporter-otlp-proto-http>=1.39.1 [4 pull requests, 2 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
crewAIInc/crewAI#4511Fetched 2026-04-08 00:41:40
View on GitHub
Comments
2
Participants
2
Timeline
14
Reactions
0
Timeline (top)
cross-referenced ×5referenced ×4commented ×2labeled ×2

crewai==1.9.3 does not support opentelemetry-exporter-otlp-proto-http==1.39.1, which causes telemetry not to be properly ingested by Langfuse, preventing me from getting a full picture.

Root Cause

uv sync x No solution found when resolving dependencies for split (markers: python_full_version >= '3.14' and sys_platform == 'win32'): `-> Because only crewai[tools]<=1.9.3 is available and crewai==1.9.3 depends on opentelemetry-exporter-otlp-proto-http>=1.34.0,<1.35.dev0, we can conclude that crewai[tools]>=1.9.3 depends on opentelemetry-exporter-otlp-proto-http>=1.34.0,<1.35.dev0. And because your project depends on crewai[tools]>=1.9.3, we can conclude that your project depends on opentelemetry-exporter-otlp-proto-http>=1.34.0,<1.35.dev0. And because your project depends on opentelemetry-exporter-otlp-proto-http>=1.38,<2.dev0 and your project requires research-algos-citations[evaluator], we can conclude that your project's requirements are unsatisfiable.

Fix Action

Fixed

PR fix notes

PR #4512: Fix #4511: Widen opentelemetry version constraints to support >=1.34.0,<2

Description (problem / solution / changelog)

Fix #4511: Widen opentelemetry version constraints to >=1.34.0,<2

Summary

The three opentelemetry dependencies (opentelemetry-api, opentelemetry-sdk, opentelemetry-exporter-otlp-proto-http) were pinned with ~=1.34.0, which resolves to >=1.34.0, <1.35.0. This prevented users from installing newer OpenTelemetry versions (e.g. >=1.38 or >=1.39.1) required by tools like Langfuse.

This PR widens the constraint to >=1.34.0,<2. crewAI only uses stable trace-related OpenTelemetry APIs (spans, tracer providers, baggage, context), and the only breaking change in recent releases (1.39.0) affects Log signal classes which crewAI does not use.

Adds a regression test suite (test_opentelemetry_version_compatibility.py) that verifies all OpenTelemetry imports used by crewAI resolve correctly and that the Telemetry singleton initializes successfully.

Review & Testing Checklist for Human

  • Verify the OpenTelemetry trace APIs used in telemetry/telemetry.py, telemetry/utils.py, crew.py, and flow/flow.py remain stable across 1.34–1.39+ (the only known breaking change in 1.39.0 is Log-related, not trace-related)
  • Confirm no other dependencies in the tree have conflicting OpenTelemetry version requirements that would cause resolution failures with the wider range
  • Test plan: In a fresh environment, install crewai alongside opentelemetry-exporter-otlp-proto-http>=1.39.1 (the version from the issue report) and verify dependency resolution succeeds and basic crew execution works

Notes

  • The added tests verify imports and minimum version at runtime but cannot truly validate that newer versions install correctly — that's a dependency resolution concern best verified manually or via the test plan above.
  • The uv.lock diff only updates specifier strings; the actual resolved versions may remain at 1.34.x until a uv lock --upgrade is run.

Link to Devin run: https://app.devin.ai/sessions/66fa037370db4cdca14e1cbc72abd12a Requested by: João

Changed files

  • lib/crewai/pyproject.toml (modified, +3/-3)
  • lib/crewai/tests/telemetry/test_opentelemetry_version_compatibility.py (added, +116/-0)
  • uv.lock (modified, +3/-3)

PR #4519: fix: relax opentelemetry version pins to allow >=1.34.0,<2

Description (problem / solution / changelog)

Summary

Relaxes the OpenTelemetry dependency version pins from ~=1.34.0 (which resolves to >=1.34.0,<1.35.0) to >=1.34.0,<2.

Problem

The current tight pins on opentelemetry-api, opentelemetry-sdk, and opentelemetry-exporter-otlp-proto-http prevent users from installing newer OpenTelemetry versions (e.g., 1.38.x, 1.39.x) alongside crewAI. This causes dependency resolution failures when users need newer OTel versions for other packages like Langfuse.

Example error:

Because crewai==1.9.3 depends on opentelemetry-exporter-otlp-proto-http>=1.34.0,<1.35.dev0
and your project depends on opentelemetry-exporter-otlp-proto-http>=1.38,<2.dev0,
your project's requirements are unsatisfiable.

Changes

  • opentelemetry-api: ~=1.34.0>=1.34.0,<2
  • opentelemetry-sdk: ~=1.34.0>=1.34.0,<2
  • opentelemetry-exporter-otlp-proto-http: ~=1.34.0>=1.34.0,<2

The OpenTelemetry libraries follow semantic versioning, so any 1.x release should be backward compatible. The <2 upper bound protects against breaking changes in a future 2.0 release.

Fixes #4511

<!-- CURSOR_SUMMARY -->

[!NOTE] Low Risk Dependency constraint-only change with no runtime logic modifications; risk is limited to potential incompatibilities if newer OpenTelemetry 1.x introduces unexpected behavior.

Overview Updates lib/crewai/pyproject.toml to relax the version constraints for opentelemetry-api, opentelemetry-sdk, and opentelemetry-exporter-otlp-proto-http from ~=1.34.0 to >=1.34.0,<2, improving compatibility with other packages that require newer OpenTelemetry 1.x versions.

<sup>Written by Cursor Bugbot for commit dd1dcaa9c947dfec634bff36e822fdd8a33f5da1. This will update automatically on new commits. Configure here.</sup>

<!-- /CURSOR_SUMMARY -->

Changed files

  • lib/crewai/pyproject.toml (modified, +3/-3)

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

Description (problem / solution / changelog)

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
<!-- CURSOR_SUMMARY -->

[!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.

<sup>Written by Cursor Bugbot for commit 4517b84f33892164407813fb661bfea890a10726. This will update automatically on new commits. Configure here.</sup>

<!-- /CURSOR_SUMMARY -->

Changed files

  • lib/crewai/pyproject.toml (modified, +3/-3)
  • uv.lock (modified, +3/-3)

PR #4626: fix: relax opentelemetry dependency constraints to allow newer versions

Description (problem / solution / changelog)

Summary

  • Relaxes opentelemetry dependency constraints from ~=1.34.0 (pinned to >=1.34.0,<1.35.0) to >=1.34.0,<2
  • The tight pinning prevented users from using newer opentelemetry versions (e.g., 1.39.1) required by other tools like Langfuse
  • Still protects against major version breaking changes with the <2 upper bound

Fixes #4511

Test plan

  • Verify crewai installs successfully with opentelemetry 1.34.x
  • Verify crewai installs successfully with opentelemetry 1.39.x
  • Verify telemetry functionality works with both versions
  • Verify no dependency conflicts with common companion packages (langfuse, etc.)

🤖 Generated with Claude Code

Changed files

  • lib/crewai/pyproject.toml (modified, +3/-3)
RAW_BUFFERClick to expand / collapse

Description

crewai==1.9.3 does not support opentelemetry-exporter-otlp-proto-http==1.39.1, which causes telemetry not to be properly ingested by Langfuse, preventing me from getting a full picture.

Steps to Reproduce

in my pyproject.toml: dependencies = [ "bedrock-agentcore", "bedrock-agentcore-starter-toolkit>=0.2.6", "boto3", "crewai[tools]>1.9.0", "fastapi>=0.128.0", "google-genai>=1.57.0", "langfuse>=3.9", "litellm>=1.75.0", "openinference-instrumentation-crewai~=0.1", "openinference-instrumentation-litellm~=0.1", "opentelemetry-exporter-otlp-proto-http~=1.38", "pydantic", ]

Expected behavior

to works

Screenshots/Code snippets

uv sync x No solution found when resolving dependencies for split (markers: python_full_version >= '3.14' and sys_platform == 'win32'): `-> Because only crewai[tools]<=1.9.3 is available and crewai==1.9.3 depends on opentelemetry-exporter-otlp-proto-http>=1.34.0,<1.35.dev0, we can conclude that crewai[tools]>=1.9.3 depends on opentelemetry-exporter-otlp-proto-http>=1.34.0,<1.35.dev0. And because your project depends on crewai[tools]>=1.9.3, we can conclude that your project depends on opentelemetry-exporter-otlp-proto-http>=1.34.0,<1.35.dev0. And because your project depends on opentelemetry-exporter-otlp-proto-http>=1.38,<2.dev0 and your project requires research-algos-citations[evaluator], we can conclude that your project's requirements are unsatisfiable.

Operating System

Ubuntu 22.04

Python Version

3.12

crewAI Version

1.9.3

crewAI Tools Version

1.9.3

Virtual Environment

Poetry

Evidence

uv sync x No solution found when resolving dependencies for split (markers: python_full_version >= '3.14' and sys_platform == 'win32'): `-> Because only crewai[tools]<=1.9.3 is available and crewai==1.9.3 depends on opentelemetry-exporter-otlp-proto-http>=1.34.0,<1.35.dev0, we can conclude that crewai[tools]>=1.9.3 depends on opentelemetry-exporter-otlp-proto-http>=1.34.0,<1.35.dev0. And because your project depends on crewai[tools]>=1.9.3, we can conclude that your project depends on opentelemetry-exporter-otlp-proto-http>=1.34.0,<1.35.dev0. And because your project depends on opentelemetry-exporter-otlp-proto-http>=1.38,<2.dev0 and your project requires research-algos-citations[evaluator], we can conclude that your project's requirements are unsatisfiable.

Possible Solution

None

Additional context

None

extent analysis

Fix Plan

To resolve the dependency conflict, we need to adjust the version of opentelemetry-exporter-otlp-proto-http to be compatible with crewai==1.9.3.

  • Update pyproject.toml to use a compatible version of opentelemetry-exporter-otlp-proto-http:
dependencies = [
  # ...
  "opentelemetry-exporter-otlp-proto-http~=1.34.0",
]
  • Run poetry update to apply the changes.

Alternatively, you can also try to update crewai to a version that supports opentelemetry-exporter-otlp-proto-http==1.39.1, if available.

Verification

After applying the fix, run poetry update and uv sync to verify that the dependencies are resolved correctly. Check the output for any error messages.

Extra Tips

  • When using Poetry, it's essential to regularly update the dependencies to ensure compatibility and security.
  • Consider using a dependency management tool like poetry or pip-compile to help resolve version conflicts.
  • If you're using a virtual environment, make sure to activate it before running poetry update or uv sync.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

to works

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

crewai - ✅(Solved) Fix [BUG] Supporting opentelemetry-exporter-otlp-proto-http>=1.39.1 [4 pull requests, 2 comments, 2 participants]