From bc5263542595cb82076da2bc6428e97fea2f44bc Mon Sep 17 00:00:00 2001 From: Vincent Sarago Date: Wed, 17 Apr 2024 08:26:49 +0200 Subject: [PATCH] prepare release 2.5.0 (#659) * prepare release 2.5.0 * Update CHANGES.md --------- Co-authored-by: Jonathan Healy --- CHANGES.md | 5 ++++- RELEASING.md | 2 +- VERSION | 2 +- stac_fastapi/api/stac_fastapi/api/version.py | 2 +- stac_fastapi/extensions/stac_fastapi/extensions/version.py | 2 +- stac_fastapi/types/stac_fastapi/types/version.py | 2 +- 6 files changed, 9 insertions(+), 6 deletions(-) diff --git a/CHANGES.md b/CHANGES.md index 18f01c0e5..f043635c0 100644 --- a/CHANGES.md +++ b/CHANGES.md @@ -2,6 +2,8 @@ ## [Unreleased] +## [2.5.0] - 2024-04-12 + ### Added * Add benchmark in CI ([#650](https://github.com/stac-utils/stac-fastapi/pull/650)) @@ -306,7 +308,8 @@ * First PyPi release! -[Unreleased]: +[Unreleased]: +[2.5.0]: [2.4.9]: [2.4.8]: [2.4.7]: diff --git a/RELEASING.md b/RELEASING.md index 8aa14afcb..afd834262 100644 --- a/RELEASING.md +++ b/RELEASING.md @@ -4,7 +4,7 @@ This is a checklist for releasing a new version of **stac-fastapi**. 1. Determine the next version. We currently do not have published versioning guidelines, but there is some text on the subject here: . 2. Create a release branch named `release/vX.Y.Z`, where `X.Y.Z` is the new version. -3. Search and replace all instances of the current version number with the new version. As of this writing, there's five different `version.py` files, and one `VERSION` file, in the repo. +3. Search and replace all instances of the current version number with the new version. As of this writing, there's 3 different `version.py` files, and one `VERSION` file, in the repo. 4. Update [CHANGES.md](./CHANGES.md) for the new version. Add the appropriate header, and update the links at the bottom of the file. 5. Audit CHANGES.md for completeness and accuracy. Also, ensure that the changes in this version are appropriate for the version number change (i.e. if you're making breaking changes, you should be increasing the `MAJOR` version number). 6. (optional) If you have permissions, run `scripts/publish --test` to test your PyPI publish. If successful, the published packages will be available on . diff --git a/VERSION b/VERSION index 158349812..437459cd9 100644 --- a/VERSION +++ b/VERSION @@ -1 +1 @@ -2.4.9 \ No newline at end of file +2.5.0 diff --git a/stac_fastapi/api/stac_fastapi/api/version.py b/stac_fastapi/api/stac_fastapi/api/version.py index bb0c7c379..1e9f3de42 100644 --- a/stac_fastapi/api/stac_fastapi/api/version.py +++ b/stac_fastapi/api/stac_fastapi/api/version.py @@ -1,2 +1,2 @@ """Library version.""" -__version__ = "2.4.9" +__version__ = "2.5.0" diff --git a/stac_fastapi/extensions/stac_fastapi/extensions/version.py b/stac_fastapi/extensions/stac_fastapi/extensions/version.py index bb0c7c379..1e9f3de42 100644 --- a/stac_fastapi/extensions/stac_fastapi/extensions/version.py +++ b/stac_fastapi/extensions/stac_fastapi/extensions/version.py @@ -1,2 +1,2 @@ """Library version.""" -__version__ = "2.4.9" +__version__ = "2.5.0" diff --git a/stac_fastapi/types/stac_fastapi/types/version.py b/stac_fastapi/types/stac_fastapi/types/version.py index bb0c7c379..1e9f3de42 100644 --- a/stac_fastapi/types/stac_fastapi/types/version.py +++ b/stac_fastapi/types/stac_fastapi/types/version.py @@ -1,2 +1,2 @@ """Library version.""" -__version__ = "2.4.9" +__version__ = "2.5.0"