Fix opentelemetry protobuf dependency conflict with Google Cloud SDKs #3414
+3,449
−3,718
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.
Fix opentelemetry protobuf dependency conflict with Google Cloud SDKs
Summary
Resolves issue #3413 by downgrading OpenTelemetry requirements from
>=1.30.0
to>=1.27.0,<1.28.0
. This fixes a dependency conflict where OpenTelemetry 1.30.0+ requiresprotobuf>=5.0
, but Google Cloud SDKs requireprotobuf<5.0
.The solution constrains OpenTelemetry to version 1.27.x which uses
protobuf<5.0,>=3.19
, allowing both CrewAI and Google Cloud SDKs to coexist. After the change, protobuf resolves to version 4.25.8 which satisfies both requirements.Changes:
pyproject.toml
to constrain opentelemetry packages to>=1.27.0,<1.28.0
uv.lock
with compatible dependency resolutionReview & Testing Checklist for Human
This is a YELLOW risk change - dependency downgrades require careful validation:
google-cloud-storage
,google-cloud-bigquery
) alongside CrewAI to confirm the protobuf conflict is resolveduv run pytest tests -v
to ensure no regressionsNotes
<1.28.0
may be overly restrictive - consider if 1.28.x/1.29.x could be allowed in future updatestest_opentelemetry_fix.py
successfully verified the fix resolves protobuf to 4.25.8Requested by: João ([email protected])
Devin session: https://app.devin.ai/sessions/18608f05b924444298bfb15d24d3d1c0