Possible bugfix and dependency conflict with langchain-core #108
Conversation
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
Compatibility with LangGraph 1.0
channels now is an attribute of builder
|
@eyurtsev @sydney-runkle Please review, latest version of langgraph-swarm is STILL NOT COMPATIBLE with Langchain v1.0 |
|
It would be much appreciated if the developers could update us what the plan is for this - if it is a quick fix or will take some time. Currently trying to work out an upgrade to v1 of langgraph and langchain-core, and this is the only package we use that is currently blocking it. Thanks |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
Hello, I created a fork to test langgraph_swarm with langchain_core and langgraph >= 1.0.0 because there was this dependency conflict. Then I got an error verifying the active_agent in the workflow creation function. I realised that nowadays the attribute channels is directly inside builder instance, not needing to get from 'schemas'. That´s why I´m creating this PR. Please take a look in this error that is possibly because of the new langraph version.