updated opentelemetry-instrumentation version to >=0.54b0

[rootflo-hardik]

• to be compatible with pipecat[tracing]

Summary by CodeRabbit

• Chores
  • Updated OpenTelemetry instrumentation dependency to version 0.54b0 or later, removing version constraints.

[coderabbitai]

📝 Walkthrough

Walkthrough

A dependency constraint for opentelemetry-instrumentation has been updated in the project configuration. The minimum version requirement was raised from 0.49b2 to 0.54b0, and the upper bound constraint was removed, allowing for more recent versions.

Changes

Cohort / File(s)	Summary
Dependency Version Update flo_ai/pyproject.toml	Updated opentelemetry-instrumentation version constraint from >=0.49b2,<0.50 to >=0.54b0, raising minimum version and removing upper bound.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Suggested reviewers

• vishnurk6247

Poem

🐰 A version bump, so simple and small,
From point-four-nine to five-four we crawl,
No ceiling now, just room to grow,
Telemetry traces in a brighter glow! ✨

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately summarizes the main change: updating the opentelemetry-instrumentation version constraint to >=0.54b0, which is the primary and only modification in the changeset.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch fix/floai_opentelemetry_instrumentation_version

Tip

Try Coding Plans. Let us write the prompt for your AI agent so you can ship faster (with fewer bugs).
Share your feedback on Discord.

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@flo_ai/pyproject.toml`:
- Line 23: The dependency declaration for opentelemetry-instrumentation
currently allows versions >=0.54b0 with no upper bound; change the constraint to
match pipecat[tracing] by pinning it to
"opentelemetry-instrumentation>=0.54b0,<1" so the project uses the tested <1.x
release range and avoids pulling in 1.0+ releases.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: c9789349-adb6-45da-b639-3e9c40efa7f3

📥 Commits

Reviewing files that changed from the base of the PR and between 39ad8c5 and 95bd092.

⛔ Files ignored due to path filters (1)

• flo_ai/uv.lock is excluded by !**/*.lock

📒 Files selected for processing (1)

• flo_ai/pyproject.toml

[coderabbitai]

⚠️ Potential issue | 🟠 Major

🧩 Analysis chain

🌐 Web query:

For the current pipecat[tracing] dependency set, what OpenTelemetry version ranges are documented or declared as compatible for opentelemetry-instrumentation, opentelemetry-api, opentelemetry-sdk, and opentelemetry-exporter-otlp?

💡 Result:

For pipecat-ai tracing extra (current main / PyPI 0.0.104 timeframe), the declared OpenTelemetry compatibility ranges are:

Package	Version range declared by pipecat-ai[tracing]
opentelemetry-instrumentation	>=0.54b0,<1 [1]
opentelemetry-api	>=1.33.0,<2 [1]
opentelemetry-sdk	>=1.33.0,<2 [1]
opentelemetry-exporter-otlp	No version range is declared by the tracing extra (Pipecat docs show using an OTLP exporter, but do not pin/specify an exporter dependency/range). [2]

Sources
[1] pipecat-ai/pipecat pyproject.toml ([project.optional-dependencies].tracing) https://github.com/pipecat-ai/pipecat/blob/main/pyproject.toml
[2] Pipecat docs: “OpenTelemetry Tracing” (exporter examples shown, no exporter version range specified) https://docs.pipecat.ai/server/utilities/opentelemetry

---

Align opentelemetry-instrumentation with pipecat[tracing] version constraints.

The upper bound was removed, allowing versions ≥1.0 to be resolved. However, pipecat[tracing] explicitly pins opentelemetry-instrumentation>=0.54b0,<1. Change this to opentelemetry-instrumentation>=0.54b0,<1 to match the tested constraint declared by pipecat[tracing].

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@flo_ai/pyproject.toml` at line 23, The dependency declaration for
opentelemetry-instrumentation currently allows versions >=0.54b0 with no upper
bound; change the constraint to match pipecat[tracing] by pinning it to
"opentelemetry-instrumentation>=0.54b0,<1" so the project uses the tested <1.x
release range and avoids pulling in 1.0+ releases.