-
Notifications
You must be signed in to change notification settings - Fork 49
chore(llma): update SDKs #367
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
Changes from all commits
5249d02
3564d58
498d1cc
ab1d79b
bdb374e
fb6ce16
46f55e0
157d53c
34cdb98
fb7d0f6
731276e
826fe9d
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,3 +1,17 @@ | ||
| # 7.0.0 - 2025-11-11 | ||
|
|
||
| NB Python 3.9 is no longer supported | ||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. let's also make clear here that we're dropping pydantic 1.0 support too |
||
|
|
||
| - chore(llma): update LLM provider SDKs to latest major versions | ||
| - openai: 1.102.0 → 2.7.1 | ||
| - anthropic: 0.64.0 → 0.72.0 | ||
| - google-genai: 1.32.0 → 1.49.0 | ||
| - langchain-core: 0.3.75 → 1.0.3 | ||
| - langchain-openai: 0.3.32 → 1.0.2 | ||
| - langchain-anthropic: 0.3.19 → 1.0.1 | ||
| - langchain-community: 0.3.29 → 0.4.1 | ||
| - langgraph: 0.6.6 → 1.0.2 | ||
|
|
||
| # 6.9.3 - 2025-11-10 | ||
|
|
||
| - feat(ph-ai): PostHog properties dict in GenerationMetadata | ||
|
|
||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,8 +1,8 @@ | ||
| try: | ||
| import langchain # noqa: F401 | ||
| import langchain_core # noqa: F401 | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @carlos-marchal-ph does this mean we would not support LC <1.* on latest posthog sdk?
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. That's correct. That's why it's also a major release. It's not ideal but at least it gives user a choice, they can still stay on 6.9. I guess we could backport it and export it as
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. hmm just trying to think through users who say have some agents working away using pre 1.0 LC but are doing all new agent dev in LC 1+ what would they do? i think maybe would be problems for them?
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. not against any of this but just thinking through what if or worse case scenarios if lots of users start complaining
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Nono, makes a lot of sense. I will implement an exported
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. yeah 100% going to only get more complicated
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
actually not even sure how possible that is actually - it might sort of be. @carlos-marchal-ph one option is to just go as-is but we just be ready with a draft pr for the
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. eg maybe we just accept that we wont know (since we dont actually have
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. That makes sense too. In any case won't merge until Monday just to be safe. |
||
| except ImportError: | ||
| raise ModuleNotFoundError( | ||
| "Please install LangChain to use this feature: 'pip install langchain'" | ||
| "Please install LangChain to use this feature: 'pip install langchain-core'" | ||
| ) | ||
|
|
||
| import json | ||
|
|
||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,5 +1,5 @@ | ||
| import pytest | ||
|
|
||
| pytest.importorskip("langchain") | ||
| pytest.importorskip("langchain_core") | ||
| pytest.importorskip("langchain_community") | ||
| pytest.importorskip("langgraph") |
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,4 +1,4 @@ | ||
| VERSION = "6.9.3" | ||
| VERSION = "7.0.0" | ||
|
|
||
| if __name__ == "__main__": | ||
| print(VERSION, end="") # noqa: T201 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i've not done a release of the python SDK for ages.
i'd be tempted to make it clear in this changelog note that this removes python 3.9 support.
i'd guess there's no user action on how they use the SDK, just whether we explicitly support the version, so no need for a "how to upgrade from 6 to 7" note
if we wanted to be very neat then we'd have a PR that removes 3.9 support, and then a PR that does the llma upgrades and we release those two changes as v7 but imho just making it clear in the changelog is enough