|
|
@ -47,7 +47,7 @@ good code into the codebase.
|
|
|
|
### 🏭Release process
|
|
|
|
### 🏭Release process
|
|
|
|
|
|
|
|
|
|
|
|
As of now, LangChain has an ad hoc release process: releases are cut with high frequency via by
|
|
|
|
As of now, LangChain has an ad hoc release process: releases are cut with high frequency via by
|
|
|
|
a developer and published to [PyPI](https://pypi.org/project/ruff/).
|
|
|
|
a developer and published to [PyPI](https://pypi.org/project/langchain/).
|
|
|
|
|
|
|
|
|
|
|
|
LangChain follows the [semver](https://semver.org/) versioning standard. However, as pre-1.0 software,
|
|
|
|
LangChain follows the [semver](https://semver.org/) versioning standard. However, as pre-1.0 software,
|
|
|
|
even patch releases may contain [non-backwards-compatible changes](https://semver.org/#spec-item-4).
|
|
|
|
even patch releases may contain [non-backwards-compatible changes](https://semver.org/#spec-item-4).
|
|
|
|