Skip to content

Commit e137eb3

Browse files
committed
Preparing for next developer iteration, 2.8.1.
Signed-off-by: dblock <[email protected]>
1 parent a74aab4 commit e137eb3

File tree

7 files changed

+18
-9
lines changed

7 files changed

+18
-9
lines changed

.github/workflows/unified-release.yml

+1-1
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ jobs:
99
strategy:
1010
fail-fast: false
1111
matrix:
12-
stack_version: ["2.8.0"]
12+
stack_version: ["2.8.1"]
1313

1414
steps:
1515
- name: Checkout

CHANGELOG.md

+9
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,15 @@
11
# CHANGELOG
22
Inspired from [Keep a Changelog](https://keepachangelog.com/en/1.0.0/)
33

4+
## [Unreleased]
5+
### Added
6+
### Updated APIs
7+
### Changed
8+
### Deprecated
9+
### Removed
10+
### Fixed
11+
### Security
12+
413
## [2.8.0]
514
### Added
615
- Added `AsyncSearch#collapse` ([827](https://github.com/opensearch-project/opensearch-py/pull/827))

COMPATIBILITY.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ The below matrix shows the compatibility of the [`opensearch-py`](https://pypi.o
99
| --- | --- | --- |
1010
| 1.0.0 | 1.0.0-1.2.4 | |
1111
| 1.1.0 | 1.3.0-1.3.7 | |
12-
| 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 |
12+
| 2.x.x | 1.0.0-2.x | client works against OpenSearch 1.x as long as features removed in 2.0 are not used |
1313

1414
## Upgrading
1515

RELEASING.md

+4-4
Original file line numberDiff line numberDiff line change
@@ -33,8 +33,8 @@ Repositories create consistent release labels, such as `v1.0.0`, `v1.1.0` and `v
3333

3434
The release process is standard across repositories in this org and is run by a release manager volunteering from amongst [maintainers](MAINTAINERS.md).
3535

36-
1. Change `Unreleased` to the version being released and add a link to its diff in [CHANGELOG](CHANGELOG.md), check version in [_version.py](opensearchpy/_version.py) and [unified-release.yml](.github/workflows/unified-release.yml), make a pull request and have it merged. See [example](https://github.com/opensearch-project/opensearch-py/pull/805).
37-
2. Check out the [upstream repo](https://github.com/opensearch-project/opensearch-py), make sure it's up-to-date with `git pull origin main`, create a tag, e.g. `git tag v2.1.0`, and push it to GitHub with `git push origin --tags`.
38-
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 along with a release issue that requires approval from another maintainer. See [example](https://github.com/opensearch-project/opensearch-py/issues/801).
36+
1. Change `Unreleased` to the version being released and add a link to its diff in [CHANGELOG](CHANGELOG.md), check version in [_version.py](opensearchpy/_version.py) and [unified-release.yml](.github/workflows/unified-release.yml), make a pull request and have it merged. See [example](https://github.com/opensearch-project/opensearch-py/pull/858).
37+
2. Check out the [upstream repo](https://github.com/opensearch-project/opensearch-py), make sure it's up-to-date with `git pull origin main`, create a tag, e.g. `git tag v2.8.0`, and push it to GitHub with `git push origin --tags`.
38+
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 along with a release issue that requires approval from another maintainer. See [example](https://github.com/opensearch-project/opensearch-py/issues/860).
3939
4. The [release-drafter#pypi-publish](.github/workflows/release-drafter.yml) workflow will publish the release to [PyPi](https://pypi.org/project/opensearch-py/).
40-
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/802).
40+
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.8.1. See [example](https://github.com/opensearch-project/opensearch-py/pull/861).

benchmarks/poetry.lock

+1-1
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.

opensearchpy/_version.py

+1-1
Original file line numberDiff line numberDiff line change
@@ -24,4 +24,4 @@
2424
# specific language governing permissions and limitations
2525
# under the License.
2626

27-
__versionstr__: str = "2.8.0"
27+
__versionstr__: str = "2.8.1"

samples/poetry.lock

+1-1
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.

0 commit comments

Comments
 (0)