Chore: add upper-bound constraints + pin litellm to exact version#71
Merged
Conversation
All production and dev dependencies now have an upper bound at the next major version (e.g. httpx>=0.28.1,<1.0.0) to guard against accidental major-version upgrades. litellm is pinned to ==1.83.7 given its history of breaking changes within minor releases. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
cosminacho
requested review from
DragosBobolea,
cristipufu and
ionmincu
as code owners
cosminacho
temporarily deployed
to
LLMGW_SETTINGS
GitHub Actions
Inactive
Follows the same reasoning as litellm itself — pin to guard against breaking changes in the litellm wrapper package. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
cosminacho
temporarily deployed
to
LLMGW_SETTINGS
GitHub Actions
Inactive
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
1 participant
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.
Summary
==1.83.7/==0.6.4) due to their history of breaking changes between minor releases.httpx>=0.28.1,<1.0.0,pydantic>=2.12.5,<3.0.0). This prevents silent major-version upgrades while still allowing compatible minor/patch updates.Constraint summary
httpx>=0.28.1>=0.28.1,<1.0.0tenacity>=9.1.4>=9.1.4,<10.0.0pydantic>=2.12.5>=2.12.5,<3.0.0pydantic-settings>=2.14.0>=2.14.0,<3.0.0uipath-platform>=0.1.34>=0.1.34,<1.0.0openai>=2.30.0>=2.30.0,<3.0.0google-genai>=1.73.1>=1.73.1,<2.0.0anthropic>=0.96.0>=0.96.0,<1.0.0litellm>=1.83.7==1.83.7(pinned)langchain>=1.2.15>=1.2.15,<2.0.0langchain-openai>=1.1.16>=1.1.16,<2.0.0langchain-google-genai>=4.2.2>=4.2.2,<5.0.0langchain-anthropic>=1.4.1>=1.4.1,<2.0.0langchain-aws>=1.4.4>=1.4.4,<2.0.0langchain-google-vertexai>=3.2.2>=3.2.2,<4.0.0langchain-azure-ai>=1.2.2>=1.2.2,<2.0.0langchain-fireworks>=1.1.0>=1.1.0,<2.0.0langchain-litellm>=0.6.4==0.6.4(pinned)Dev deps (
pytest,pyright,ruff, etc.) also got upper-bounded similarly.Which packages
pyproject.tomlchanged; skips 1.9.7 which was consumed by a langchain-only release).pyproject.tomlchanged,uipath-llm-clientfloor bumped to 1.9.8).Test plan
uv sync --all-extrasresolves cleanlyruff checkruff format --checkpyrightpytest tests— 1522 passed, 736 skipped, 9 xpassed🤖 Generated with Claude Code