chore(deps): refresh dependencies with LiteLLM compatibility cap#1051
Merged
Conversation
Signed-off-by: phernandez <paul@basicmachines.co>
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.
Why
uv sync --upgraderesolved LiteLLM 1.92.0, which replaced the universal Python wheel with a native Rust bridge. On macOS, uv falls back to the source distribution and the bundled PyO3 0.23.5 rejects Python 3.14.The dependency refresh also upgrades
ty, whose current default exits nonzero for advisory warnings as well as type errors.What
tyadvisory diagnostics visible without making them fail the typecheck gateVerification
uv sync --upgradelitellm==1.91.3importuv lock --checkuv run pytest tests/repository/test_litellm_provider.py test-int/semantic/test_litellm_live_harness.py -q— 32 passedjust package-checkjust typecheck— passed with existing Python 3.14 asyncio deprecation warnings visibleLocal gate notes
just fast-checkinvalidated testmon after the environment refresh and entered the full suite. Semantic setup could not connect to the configured OrbStack Docker socket; representative later failures passed when rerun in isolation.just doctorcompleted the file-to-database, database-to-file, search, and embedding checks, then hit the existing cleanup guard that prevents deleting the only default project in an isolated configuration.