Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: Update langchain-astradb to version >=0.5.0 and address dependency conflicts #4046

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

edwinjosechittilappilly
Copy link
Collaborator

This pull request updates the langchain-astradb package to version >=0.5.0, along with relevant package upgrades to ensure compatibility and improved functionality.

However, please note that the crewai package is currently in conflict as it does not support langchain version 0.3.0 or above. This conflict needs to be addressed to maintain compatibility across the project.

Changes Made:

  • Updated langchain-astradb to >=0.5.0.
  • Upgraded relevant packages to align with the new version.
  • Identified and documented the conflict with crewai.
  • Changes also made in base.

langchain-astradb has been updated to version >=0.5.0. Relevant packages have also been upgraded. However, crewai is in conflict as it doesn't support langchain 0.3.0 or above.
Copy link

This pull request is automatically being deployed by Amplify Hosting (learn more).

Access this pull request here: https://pr-4046.dmtpw4p5recq1.amplifyapp.com

Copy link
Contributor

@ogabrielluiz ogabrielluiz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks, Edwin!

@@ -89,13 +89,12 @@ dependencies = [
"kubernetes>=30.1.0",
"firecrawl-py>=0.0.16",
"json-repair>=0.25.2",
"langchain-nvidia-ai-endpoints==0.1.6",
"langchain-nvidia-ai-endpoints>=0.1.6",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd say find the version that works with this update and lock it on that.
Same for the others

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Any reason you recommend locking to a specific version? I ask because we ran into this several times with the previous project, where users doing dev work pulled in specific upgraded versions of dependencies. I suspect that would happen much less often with Langflow, but curious why we wouldn't keep them as relaxed as possible

@jordanrfrazier
Copy link
Collaborator

CrewAI tracking issue to upgrade lc - crewAIInc/crewAI#1352

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants