upd: Bump ruby_llm dependency and remove PATCH semantic version constraint#61
Merged
aakashb95 merged 1 commit intoApr 20, 2026
Conversation
…raint Removing the PATCH semantic version constraint will allow users of ai-agents to use any non-breaking new version of ruby_llm, even if ruby_llm is not released for those new versions. It is safe as long as ruby_llm respects semantic versioning, which apparently is assumed given that the semantic operator ~> is already used for version constraint.
✅ Deploy Preview for ruby-ai-agents canceled.
|
Member
|
Hey @Muriel-Salvan thanks for the PR. We'll test this internally and get it merged soon |
aakashb95
approved these changes
Apr 20, 2026
Contributor
|
Thanks for your contribution! |
aakashb95
added a commit
that referenced
this pull request
Apr 20, 2026
* chore: release version 0.10.0 Bumps MINOR for the ruby_llm dependency major upgrade (~> 1.9.1 → ~> 1.14) merged in #61, along with provider-specific params support (#44) and internal refactors since 0.9.1. * chore: drop internal refactor entries from 0.10.0 CHANGELOG * chore: note internal refactors in 0.10.0 CHANGELOG
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.
Removing the PATCH semantic version constraint will allow users of ai-agents to use any non-breaking new version of ruby_llm, even if ruby_llm is not released for those new versions. It is safe as long as ruby_llm respects semantic versioning, which apparently is assumed given that the semantic operator ~> is already used for version constraint.