Plans for upgrading to langchain-core 1.x? #12418
MatthiasHowellYopp
started this conversation in
General
Replies: 1 comment 1 reply
-
|
In version 1.9.0 they added support for LangChain >1.0 (PR #11114). |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Context
We're developing new integrations for Langflow that depend on newer versions of langchain partner packages (specifically
langchain-aws>=1.0.0andlangchain-google-genai>=4.0.0). Both of these requirelangchain-core>=1.0.0.Langflow currently pins
langchain-core>=0.3.81,<1.0.0, which makes it impossible to use these newer packages without dependency conflicts.Specific cases
langchain-aws 1.x — Added
ValkeyVectorStorefor native Valkey vector search support. Only available in langchain-aws>=1.0.0, which requires langchain-core>=1.0.0.langchain-google-genai 4.x — Migrated from the deprecated
google-generativeaiSDK to the newgoogle-genaiSDK. This also resolves a protobuf 5 vs 6 conflict (valkey-glide requires protobuf>=6, whilegoogle-ai-generativelanguageused by the older SDK pins protobuf<6).Question
Are there plans to upgrade Langflow to langchain-core 1.x? If so, is there a rough timeline or tracking issue we can follow?
We'd like to contribute Valkey components (vector store + chat memory + Celery broker support) but the dependency constraint is currently a blocker for using the official
langchain-awsValkey integration.Workaround
We've implemented a custom
ValkeyVectorStorewrapper that usesvalkey-glidedirectly (bypassinglangchain-aws), but this requires an unreleased version of valkey-glide with search module support, and the protobuf conflict remains when both valkey-glide and google-generativeai are installed.Beta Was this translation helpful? Give feedback.
All reactions