chore: merge release/0.6.0 back to develop#160
Merged
Merged
Conversation
- Bump version 0.5.2 -> 0.6.0 (new public checkpointer capabilities since 0.5.2: copy_thread/delete_for_runs + non-blocking async + concurrency fixes — minor bump). - Raise production dependency floors to a 4.x-capable, mutually-consistent stack: langchain-core >=1.4, langgraph >=1.2, langgraph-checkpoint >=4.1. copy_thread/delete_for_runs/prune are langgraph-checkpoint 4.x base capabilities, and langgraph 1.2.0 is the first release that requires langgraph-checkpoint>=4.1.0 + langchain-core>=1.4.0, so the three floors resolve together. Previously the declared floor (langgraph-checkpoint 3.0.1) imported fine but lacked the advertised 4.x capabilities. - README: add a Version Compatibility section with a per-release support table and explicit guidance so LangChain users pick 0.6.x (LangChain 1.x) vs 0.5.x (older stacks); refresh stale 0.5.1 references and Requirements. Lock regenerated with Poetry 2.1.3 (resolves langchain-core 1.4.7 / langgraph 1.2.5 / langgraph-checkpoint 4.1.1). 125 unit tests + embedded conformance pass; ruff clean.
Merged
webup
changed the title
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
1 participant
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.
Summary
Prepares the 0.6.0 release.
0.5.2 → 0.6.0(minor): adds new public checkpointer API since 0.5.2 —copy_thread/delete_for_runs(+async), non-blocking async methods, executor lifecycle,max_workers.langchain-core >=1.4.0,<2.0.0langgraph >=1.2.0,<2.0.0langgraph-checkpoint >=4.1.0,<5.0.0Why raise the floor
copy_thread/delete_for_runs/prunearelanggraph-checkpoint4.x base capabilities (verified: absent fromBaseCheckpointSaverin 3.0.1, present in 4.x). The previous declared floor (langgraph-checkpoint>=3.0.1) imported without error but did not provide the capabilities this package now advertises and conformance-tests.langgraph 1.2.0is the first release that requireslanggraph-checkpoint>=4.1.0andlangchain-core>=1.4.0, so pinning all three to that line keeps the floors internally consistent (an isolatedlanggraph-checkpoint>=4bump would have contradicted the oldlanggraph 0.6.11floor, which caps checkpoint<4.0.0).Compatibility impact (documented in README)
This moves the package to the LangChain / LangGraph 1.x line. Users on older stacks should pin
langchain-oceanbase>=0.5,<0.6. The README table spells out which release to choose.Testing
poetry lockregenerated with Poetry 2.1.3 (matches CI); resolves langchain-core 1.4.7 / langgraph 1.2.5 / langgraph-checkpoint 4.1.1.poetry check --lockpasses.ruff check/formatclean.Note
No
CHANGELOG.mdexists in the repo yet (README links to one). Out of scope here; worth adding in a follow-up.