Versioning ↗

Documentation Index#

Fetch the complete documentation index at: https://docs.langchain.com/llms.txt Use this file to discover all available pages before exploring further.

Our OSS version numbers follow the format: MAJOR.MINOR.PATCH, as defined by Semantic Versioning.

• Major: Breaking API updates that require code changes.
• Minor: New features and improvements that maintain backward compatibility.
• Patch: Bug fixes and minor improvements.

For example:

• 1.0.0: First stable release with production-ready APIs
• 1.1.0: New features added in a backward-compatible manner
• 1.0.1: Backward-compatible bug fixes

API stability#

We communicate the stability of our APIs as follows:

Stable APIs#

All APIs without special prefixes are considered stable and ready for production use. We maintain backward compatibility for stable features and only introduce breaking changes in major releases.

Beta APIs#

APIs marked as beta are feature-complete but may undergo minor changes based on user feedback. They are safe for production use but may require small adjustments in future releases.

Alpha APIs#

APIs marked as alpha are experimental and subject to significant changes. Use these with caution in production environments.

Deprecated APIs#

APIs marked as deprecated will be removed in future major releases. When possible, we specify the intended version of removal. To handle deprecations:

1. Switch to the recommended alternative API
2. Follow the migration guide (released alongside major releases)
3. Use automated migration tools when available

Internal APIs#

Certain APIs are explicitly marked as “internal” in a couple of ways:

• Some documentation refers to internals and mentions them as such. If the documentation says that something is internal, it may change.
• Functions, methods, and other objects prefixed by a leading underscore (_). This is the standard Python convention of indicating that something is private; if any method starts with a single _, it’s an internal API.
  • Exception: Certain methods are prefixed with _ , but do not contain an implementation. These methods are meant to be overridden by sub-classes that provide the implementation. Such methods are generally part of the Public API of LangChain.

Release cycles#

import { version } from "langchain/package.json";
console.log(version);

import { version } from "@langchain/langgraph/package.json";
console.log(version);

# Upgrade to the latest version
npm update langchain @langchain/core

# Install a specific version
npm install langchain@1.0.0 @langchain/core@1.0.0

# Upgrade to the latest version
npm update @langchain/langgraph

# Install a specific version
npm install @langchain/langgraph@1.0.0