{{ message }}
fix(deps): support google-adk>=1.32.0 (migrate optional deps to openai 2.x)#597
Merged
Conversation
google-adk 2.x moved litellm and sqlalchemy behind extras ([extensions]/[db]); veadk uses both unconditionally (LiteLlm models, sessions). Declare them directly and relax google-adk to >=1.32.0 so a bare install works across 1.x and 2.x. Verified by a fresh install: resolves google-adk 2.2.0 + litellm 1.83.14 + sqlalchemy 2.0.50, 'uv pip check' clean, module imports + a real model invoke all pass.
…o 2.x google-adk 1.x shipped litellm+sqlalchemy in base and pinned openai 1.x via its RAG deps; 2.x moved litellm/sqlalchemy behind extras and its litellm requires openai 2.x. veadk needs litellm (LiteLlm) + sqlalchemy (sessions) unconditionally, which forces openai 2.x and clashed with the openai-1.x pins in the optional extras (mem0ai 0.1.118, llama-index 0.14.0 stack). Changes: - relax google-adk to >=1.32.0; declare litellm>=1.83.7,<=1.83.14 and sqlalchemy>=2,<3 in base (adk's own ranges). - bump the openai-1.x pinned optional deps to openai-2.x compatible versions: llama-index* to >=, mem0ai to >=1.0.0,<2 (1.0.x keeps the kwargs add()/search() API veadk uses; 2.x switched to an options object). Verified --all-extras resolves on py3.10 and py3.13 (google-adk 2.2.0, litellm 1.83.14, openai 2.24.0, llama-index 0.14.22, mem0ai 1.0.11, sqlalchemy 2.0.50); uv pip check clean; imports, a local KnowledgeBase RAG flow, and a real model invoke all pass.
yaozheng-fang
changed the title
zakahan
approved these changes
Jun 10, 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
2 participants
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.
What
Make veadk install & run across google-adk 1.x and 2.x (
google-adk>=1.32.0).Why
litellmandsqlalchemybehind extras(
[extensions]/[db]). veadk uses both unconditionally (LiteLlm models,sessions), so a bare install on adk 2.x failed at import. Declare themdirectly in base.
litellm(>=1.83.7) pins openai 2.x (openai==2.24.0/2.30.0),which clashed with veadk's optional extras that pinned openai 1.x
(
mem0ai==0.1.118→openai<1.110;llama-index==0.14.0stack →llama-index-llms-openai0.5.x → openai 1.x). Resolving--all-extraswastherefore unsatisfiable. Migrate those optional deps to openai-2.x-compatible
versions.
Changes (
pyproject.tomlonly)google-adk→>=1.32.0.litellm>=1.83.7,<=1.83.14,sqlalchemy>=2,<3(adk's own ranges).[extensions]: relax thellama-index*pins to>=(resolve to 0.14.22 +llama-index-llms-openai0.7.9, which support openai 2.x).[database]:mem0ai==0.1.118→mem0ai>=1.0.0,<2.>=1.0lifts theopenai<1.110cap;<2keeps the kwargsadd()/search()API veadk'smem0 backend uses (mem0 2.x switched to an
optionsobject — would break atruntime).
Verification
uv pip compile --all-extrasresolves on py3.10 and py3.13. Fresh--all-extrasinstall (252 pkgs): google-adk 2.2.0, litellm 1.83.14,openai 2.24.0, llama-index 0.14.22, mem0ai 1.0.11, sqlalchemy 2.0.50.
uv pip check→ clean.mem0.MemoryClient.add/searchsignatures match veadk's usage on 1.0.x.Note
Behavior change: fresh installs now resolve to google-adk 2.x. The
Agent/Runner/sessions, RAG, and mem0-signature paths are verified; reviewers may
still want to smoke-test the full RAG/long-term-memory flows against live
backends (OpenSearch/Redis/Viking/mem0).
🤖 Generated with Claude Code