📕 Package versioning

As of now, LangChain has an ad hoc release process: releases are cut with high frequency by a maintainer and published to NPM. The different packages are versioned slightly differently.

@langchain/core

@langchain/core is currently on version 0.1.x.

As @langchain/core contains the base abstractions and runtime for the whole LangChain ecosystem, we will communicate any breaking changes with advance notice and version bumps. The exception for this is anything marked as beta (you can see this in the API reference and will see warnings when using such functionality). The reason for beta features is that given the rate of change of the field, being able to move quickly is still a priority.

Minor version increases will occur for:

• Breaking changes for any public interfaces marked as beta.

Patch version increases will occur for:

• Bug fixes
• New features
• Any changes to private interfaces
• Any changes to beta features

langchain

langchain is currently on version 0.2.x

Minor version increases will occur for:

• Breaking changes for any public interfaces NOT marked as beta.

Patch version increases will occur for:

• Bug fixes
• New features
• Any changes to private interfaces
• Any changes to beta features.

@langchain/community

@langchain/community is currently on version 0.2.x

All changes will be accompanied by the same type of version increase as changes in langchain.

Partner Packages

Partner packages are versioned independently.