github/langchain
1
0
Fork 0
mirror of https://github.com/hwchase17/langchain.git synced 2025-06-23 15:19:33 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs: update typos in release_policy.mdx (#31397)

Browse Source 
Deleted two outdated phrases that were reflecting the current versions
of packages at the time i.e.: 1-"langchain-community is currently on
version 0.2.x." 2-langchain-"experimental is currently on version 0.0.x"
This commit is contained in:
Hanieh Moshki 2025-05-28 11:45:55 -04:00 committed by GitHub
parent 60119b9ba6
commit 7b8b8a26e7
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 2 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
docs/docs/versions/release_policy.mdx
View File

@ -30,8 +30,6 @@ From time to time, we will version packages as **release candidates**. These are
### `langchain-community` ### `langchain-community`
`langchain-community` is currently on version `0.2.x`.
Minor version increases will occur for: Minor version increases will occur for:
- Updates to the major/minor versions of required `langchain-x` dependencies. E.g., when updating the required version of `langchain-core` from `^0.2.x` to `0.3.0`. - Updates to the major/minor versions of required `langchain-x` dependencies. E.g., when updating the required version of `langchain-core` from `^0.2.x` to `0.3.0`.
@ -49,7 +47,7 @@ However, if an external API makes a breaking change then breaking changes to the
### `langchain-experimental` ### `langchain-experimental`
`langchain-experimental` is currently on version `0.0.x`. All changes will be accompanied with patch version increases. All changes will be accompanied with patch version increases.
## Release cadence ## Release cadence
@ -99,4 +97,4 @@ When a feature is deprecated, it will continue to work in the current and next m
Since we're expecting to space out minor releases by at least 2-3 months, this means that a feature can be removed within 2-6 months of being deprecated. Since we're expecting to space out minor releases by at least 2-3 months, this means that a feature can be removed within 2-6 months of being deprecated.
In some situations, we may allow the feature to remain in the code base for longer periods of time, if it's not causing issues in the packages, to reduce the burden on users. In some situations, we may allow the feature to remain in the code base for longer periods of time, if it's not causing issues in the packages, to reduce the burden on users.