Skip to main content

Buyer guide

LangGraph Version Pinning & Upgrade Checklist

How long LangChain supports LangGraph 1.x and 0.4, and the two October 2026 security advisories that set minimum package versions.

Reading time
3 min read
Sources
16 cited

Pin LangGraph together with its checkpointer, CLI, API and SDK packages. Upgrade inside the 1.x long-term-support window that replaced the fast-changing 0.x line in October 2025, and test that saved checkpoints still load after every code or state schema change. Teams still on 0.4 have until December 2026.

When you need this

  • Your agents still run on LangGraph 0.x, whose 0.4 line receives fixes only until December 2026.
  • An upgrade broke an import, a checkpointer, or the CLI in the past.
  • You are about to change the state schema of a graph with open threads.

Evaluation criteria

  1. Support window

    Which versions does LangChain support, and until when?

    Look forLangGraph 1.0 is a long-term-support (LTS) release, developed until 2.0 and then maintained for at least a year. Breaking changes come only in major releases, and deprecated features keep working for at least one minor release. The GitHub release notes through 1.2.18 on October 26, 2026 list no breaking change in 1.x. LangGraph 0.4 gets security patches and critical fixes until December 2026.

  2. Release pace

    How often will updates arrive?

    Look forExpect minor releases every one to two months and patches as often as weekly. PyPI lists 38 stable LangGraph releases between October 12, 2025 and October 12, 2026, from 1.0.0 to 1.2.14.

  3. Pin the set

    Which packages move together?

    Look forPin langgraph, the checkpointer package, langgraph-cli, langgraph-api, and the SDK together and upgrade them as a set. Two advisories set floors. CVE-2026-115883 (Moderate, October 21, 2026): in the Postgres and SQLite stores, a namespace label containing a dot can read, overwrite, or delete another namespace's items. Upgrade to langgraph-checkpoint-postgres 3.1.3 or langgraph-checkpoint-sqlite 3.1.2, which require langgraph-checkpoint 4.3.0. Self-hosted Agent Servers need 0.15.5 or 0.16.2. InMemoryStore is unaffected. CVE-2026-115885 (Moderate, October 23, 2026): langgraph deploy --verbose in langgraph-cli 0.4.15 to 0.4.31 printed a registry push token that lives up to 12 hours. Use CLI 0.4.32 or later and purge CI logs from verbose deploys. Use langgraph 1.2.17 (October 24, 2026) or later. Earlier releases dropped an explicit recursion_limit equal to the default, so a looping graph could run past the step limit you set. Add a test that a deliberate loop stops at your configured limit. Engineers have reported a 0.4.4 release that failed on a basic import hours after publication. They also reported a Postgres saver release that could not read existing checkpoints, and a CLI that pinned an older API package.

  4. Deprecated APIs

    What did v1 deprecate?

    Look forv1 deprecates the prebuilt create_react_agent in favor of LangChain's create_agent. The graph API and the execution model stay the same. LangGraph 1.x requires Python 3.10 or later.

  5. State schema changes

    Can old checkpoints still load after a change?

    Look forCheckpoints store serialized state, so renaming or retyping a field can stop open threads from restoring. Add fields with defaults, migrate or close open threads before removing a field, and test resume from a checkpoint written by the previous release.

  6. Docs and examples

    Do your references match your version?

    Look forEngineers report course notebooks and tutorials that broke within weeks, and docs that lagged releases. Check examples against the installed version, and read the GitHub release notes before each minor upgrade.

Questions to ask vendors

  1. Which LangGraph version does each service run, and is any still on 0.x?
  2. Are the checkpointer, CLI, API, and SDK packages pinned with it?
  3. Does CI resume a thread from a checkpoint written by the previous release?
  4. Who reads release notes before a minor upgrade?

Red flags

  • Unpinned langgraph or checkpointer dependencies in production.
  • 0.x services with no upgrade plan before December 2026.
  • State fields renamed while threads are open.
  • Tutorial code copied without checking the installed version.

Products in this piece

Sources

Official documentation
11
Public source
5
  1. LangChain docs: Release policy (LangGraph LTS)Official documentationdocs.langchain.com
  2. LangGraph docs: What's new in LangGraph v1Official documentationdocs.langchain.com
  3. LangChain blog: LangChain and LangGraph reach v1.0 (Oct 22, 2025)Official documentationlangchain.com
  4. LangGraph releases on GitHubOfficial documentationgithub.com
  5. LangGraph release 1.1.0 on GitHub: type-safe streaming and invoke (Mar 10, 2026)Official documentationgithub.com
  6. LangGraph release 1.1.8 on GitHub: fix for a type check that broke OpenTelemetry instrumentation (Apr 17, 2026)Official documentationgithub.com
  7. langgraph on PyPI (release history)Official documentationpypi.org
  8. LangGraph docs: Checkpointers and durability modesOfficial documentationdocs.langchain.com
  9. GitHub Advisory GHSA-6hmw-9432-67qq (CVE-2026-115883): namespace labels in Postgres and SQLite stores (Oct 21, 2026)Public sourcegithub.com
  10. LangGraph security advisory GHSA-8prr-f582-jqq3 (CVE-2026-115885): registry push token in langgraph deploy --verboseOfficial documentationgithub.com
  11. LangGraph release 1.2.17 on GitHub (Oct 24, 2026)Official documentationgithub.com
  12. LangGraph release 1.2.18 on GitHub (Oct 26, 2026)Official documentationgithub.com
  13. LangGraph issue #4706: 0.4.4 ModuleNotFoundError for langgraph.cache (May 15, 2025)Public sourcegithub.com
  14. LangGraph issue #5677: AsyncPostgresSaver 2.0.23 fails to read channel values (Jul 27, 2025)Public sourcegithub.com
  15. LangGraph issue #6706: langgraph-cli incompatible with langgraph-api 0.7.0 and later (Jan 21, 2026)Public sourcegithub.com
  16. Sagi Medina (Qodo): Why we chose LangGraph to build our coding agent (Mar 21, 2025)Public sourceqodo.ai