From 626e90e2cd27f8082f84a97956192624c334d3c4 Mon Sep 17 00:00:00 2001 From: dblock Date: Mon, 19 Aug 2024 18:58:07 -0400 Subject: [PATCH] Update compatibility matrix. Signed-off-by: dblock --- COMPATIBILITY.md | 2 +- RELEASING.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/COMPATIBILITY.md b/COMPATIBILITY.md index bc35d192..60419c89 100644 --- a/COMPATIBILITY.md +++ b/COMPATIBILITY.md @@ -9,7 +9,7 @@ The below matrix shows the compatibility of the [`opensearch-py`](https://pypi.o | --- | --- | --- | | 1.0.0 | 1.0.0-1.2.4 | | | 1.1.0 | 1.3.0-1.3.7 | | -| 2.x.x | 1.0.0-2.14.0 | client works against OpenSearch 1.x as long as features removed in 2.0 are not used | +| 2.x.x | 1.0.0-2.16.0 | client works against OpenSearch 1.x as long as features removed in 2.0 are not used | ## Upgrading diff --git a/RELEASING.md b/RELEASING.md index fee20a8e..18c06287 100644 --- a/RELEASING.md +++ b/RELEASING.md @@ -37,4 +37,4 @@ The release process is standard across repositories in this org and is run by a 2. Create a tag, e.g. v2.1.0, and push it to the GitHub repo. 3. The [release-drafter#draft-a-release](.github/workflows/release-drafter.yml) workflow will be automatically kicked off and a draft release will be created. 4. The [release-drafter#pypi-publish](.github/workflows/release-drafter.yml) workflow will publish the release to [PyPi](https://pypi.org/project/opensearch-py/). -5. Add an "Unreleased" section to CHANGELOG, and increment version in [_version.py](opensearchpy/_version.py) to the next patch release, e.g. v2.1.1. See [example](https://github.com/opensearch-project/opensearch-py/pull/593). \ No newline at end of file +5. Add an "Unreleased" section to [CHANGELOG](CHANGELOG.md), update the [COMPATIBILITY](COMPATIBILITY.md) matrix, and increment version in [_version.py](opensearchpy/_version.py) to the next patch release, e.g. v2.1.1. See [example](https://github.com/opensearch-project/opensearch-py/pull/593). \ No newline at end of file