Repository navigation
fix(sdk-python): require telemetry-dev 0.3.0 in the python integrations - #122
Merged
Merged
Conversation
The Anthropic, Bedrock, Google GenAI, LiteLLM, OpenAI, and OpenRouter integrations now need telemetry-dev 0.3.0 or later, so installing or upgrading one also brings the core that sends to api.telemetry.dev by default and has the prompt fetch fixes. Each integration's tests pass against telemetry-dev 0.3.0.
Merged
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The six Python integrations (Anthropic, Bedrock, Google GenAI, LiteLLM, OpenAI, OpenRouter) now require
telemetry-dev>=0.3.0. Before this, an app could upgrade an integration and keep an older core, which still sends toingest.telemetry.devby default and lacks the prompt fetch fixes in 0.3.1.ingest.telemetry.devstays supported, so this only changes which core an install resolves.Each integration's tests pass against
telemetry-dev0.3.0 installed from PyPI, so the new floor is a version the code runs on. Theuv.lockfiles point at the local core by path and record no version range, so they do not change.This is a
fix, so release-please takes the integrations from 0.2.0 to 0.2.1. Their 0.2.0 release already announced the new default host.