fix(deps): widen OpenTelemetry compatibility range - #7288
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Team Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (2)
Included review availability: Your plan provides up to 10 included reviews per hour; 9 remain after this review. 📝 WalkthroughWalkthroughChangesOpenTelemetry dependency constraints
Suggested reviewers: Merge Risk: ⚪ Minimal · up to This change widens aligned OpenTelemetry dependency ranges to permit compatible newer 1.x releases, including protobuf 7.x-compatible resolution. The package constraints and lockfile metadata are consistent, with no remaining merge-readiness risk identified. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
b8fabcc to
e211a2e
Compare
Signed-off-by: kiwoong <rldnddbs@naver.com>
e211a2e to
372e0ac
Compare
…nc-crewAI-issue-7287
Title: fix(deps): widen OpenTelemetry compatibility range
Related issue
Fixes #7287
Summary
>=1.42,<2in bothcrewaiandcrewai-core.uv.lockwithout unrelated upgrades.Test evidence
uv pip compilewith the new ranges andprotobuf>=7.34,<8resolves OpenTelemetry/proto 1.44.0 with protobuf 7.35.1.UV_CACHE_DIR=/tmp/gitcontribute-7287-uv-cache-copy rtk uv lock --check --offline --python /usr/bin/python3.12rtk git diff --checkRisks or notes for maintainers
llm-generatedlabel when opening this PR.