-
Notifications
You must be signed in to change notification settings - Fork 30
updated opentelemetry-instrumentation version to >=0.54b0 #242
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
vizsatiz
merged 1 commit into
develop
from
fix/floai_opentelemetry_instrumentation_version
Mar 11, 2026
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🧩 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
tracingextra (currentmain/ PyPI 0.0.104 timeframe), the declared OpenTelemetry compatibility ranges are: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-otlptracingextra (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-instrumentationwithpipecat[tracing]version constraints.The upper bound was removed, allowing versions ≥1.0 to be resolved. However,
pipecat[tracing]explicitly pinsopentelemetry-instrumentation>=0.54b0,<1. Change this toopentelemetry-instrumentation>=0.54b0,<1to match the tested constraint declared bypipecat[tracing].🤖 Prompt for AI Agents