Skip to main content
This page explains the LangChain and LangGraph release policies. Click on the tabs below to view the release policies for each:
  • LangChain
  • LangGraph
The LangChain ecosystem is composed of different component packages (e.g., @langchain/core, langchain, @langchain/community, partner packages, etc.)

​
Release cadence

With the release of LangChain 1.0, minor releases (e.g., from 1.0.x to 1.1.0) of langchain and @langchain/core follow semantic versioning and may be released frequently. Minor releases contain new features and improvements but do not include breaking changes.Patch versions are released frequently, up to a few times per week, as they contain bug fixes and minor improvements.

​
API stability

The development of LLM applications is a rapidly evolving field, and we are constantly learning from our users and the community. As such, we expect that the APIs in langchain and @langchain/core will continue to evolve to better serve the needs of our users.With LangChain 1.0’s adoption of semantic versioning:
  • Breaking changes to the public API will only occur in major version releases (e.g., 2.0.0)
  • Minor version bumps (e.g., 1.0.0 to 1.1.0) add new features without breaking changes
  • Patch version bumps (e.g., 1.0.0 to 1.0.1) contain bug fixes and minor improvements
We will generally try to avoid making unnecessary changes, and will provide a deprecation policy for features that are being removed.

​
Stability of other packages

The stability of other packages in the LangChain ecosystem may vary:
  • Partner packages maintained by LangChain (such as langchain-openai and langchain-anthropic) follow semantic versioning and are expected to be stable post 1.0. Other partner packages may follow different stability and versioning policies, and users should refer to the documentation of those packages for more information.
  • @langchain/community is a community maintained package that contains 3rd party integrations. Due to the nature of community contributions and third-party dependencies, @langchain/community does not follow the same strict semantic versioning policy as langchain and @langchain/core. See the “Special considerations” section under Long-term support for more details.

​
Deprecation policy

We will generally avoid deprecating features until a better alternative is available.With LangChain 1.0’s semantic versioning approach, deprecated features will continue to work throughout the entire 1.x release series. Breaking changes, including the removal of deprecated features, will only occur in major version releases (e.g., 2.0).When a feature is deprecated in langchain or @langchain/core, we will:
  • Clearly mark it as deprecated in the code and documentation
  • Provide migration guidance to the recommended alternative
  • Provide security updates for the deprecated feature through all 1.x minor releases
In some situations, we may allow deprecated features to remain in the code base even longer if they are not causing maintenance issues, to further reduce the burden on users.

​
Long-term support (LTS)

LangChain follows a long-term support (LTS) policy to provide stability for production applications:

​
Release status definitions

Packages are marked with one of the following statuses:
  • ACTIVE: Current active development, includes bug fixes, security patches, and new features
  • MAINTENANCE: Receives all security patches and critical bug fixes, but no new features

​
Current LTS releases

LangChain 1.0 is designated as an LTS release:
  • Status: ACTIVE until the release of 2.0
  • Support period: After 2.0 is released, 1.0 will enter MAINTENANCE mode for at least 1 year
  • Semver compliance: Users can upgrade between minor versions (e.g., 1.0 to 1.1) without breaking changes

​
Legacy version support

LangChain 0.3:
  • Status: MAINTENANCE mode
  • Support period: Until December 2026
  • Support includes: Security patches and critical bug fixes

​
Special considerations

@langchain/community 1.0: Due to the nature of community contributions and third-party integrations, @langchain/community may have breaking changes on minor releases.
Edit the source of this page on GitHub.
Connect these docs programmatically to Claude, VSCode, and more via MCP for real-time answers.