Add support for RubyLLM 2.0 - #218
Merged
Merged
Conversation
Abhijeet Prasad (AbhiPrasad)
left a comment
Member
There was a problem hiding this comment.
do we want to version cassettes by library version? And then have a test matrix of versions we test against?
Stephen Belanger (Qard)
approved these changes
Sep 22, 2026
Stephen Belanger (Qard)
left a comment
Contributor
There was a problem hiding this comment.
Generally LGTM, but I agree it might be a good idea to version things explicitly. The different endpoints is an implementation detail which could change, that doesn't explicitly reflect the version.
Collaborator
Author
|
Good suggestion: put them under major versions. |
Abhijeet Prasad (AbhiPrasad)
approved these changes
Sep 22, 2026
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.
Adds support for
ruby_llm 2.0, released 2026-09-18. Our integration covered 1.x only, and 2.0 is a breaking major release that moves most of what the instrumentation reads.What 2.0 changed
message.content.attachmentson aRubyLLM::Contentmessage.attachments;Contentremoved, content is aStringtool.params_schema,Providers::OpenAI::Toolstool.parameters_schema; providerToolsmodule removed{}param ..., desc:parameter ..., description:Chat#with_toolwith_toolsremainswith_tools, valid on bothVersion differences are handled by duck-typing what the object exposes rather than branching on a version number, so 1.x and 2.0 run the same code path.