From ccc26e4f46e836c25b55b371e35b686cee2d1c1f Mon Sep 17 00:00:00 2001 From: Arjo Segers Date: Wed, 8 Apr 2026 10:10:06 +0200 Subject: [PATCH] Defined v2.16 --- doc/source/history.rst | 12 ++++++------ pyproject.toml | 2 +- 2 files changed, 7 insertions(+), 7 deletions(-) diff --git a/doc/source/history.rst b/doc/source/history.rst index ccdd38c..0cc2e5d 100644 --- a/doc/source/history.rst +++ b/doc/source/history.rst @@ -129,7 +129,7 @@ A summary of the versions and changes. | Updates for access to Copernicus DataSpace: use STAC API to inquire, and download from S3 buckets. | *(2026-03)* -* | *vx.y* +* | *v2.16* | Removed support for SO\ :sub:`2` COBRA product as this has become operational. | *(2026-04)* @@ -165,7 +165,7 @@ A wishlist of developments. How to create a version tag =========================== -Example for tag "v2.15". +Example for tag "v2.16". 1. Update file formatting following conventions. @@ -185,17 +185,17 @@ Example for tag "v2.15". c. Change the release tag that will also be imported to the documenation in the `pyproject.toml <../../../pyproject.toml>`_ file:: - release = "2.14" + release = "2.16" d. Commit and push these changes:: - git commit -m 'Defined v2.15' . + git commit -m 'Defined v2.16' . git push 4. Tag and push the code to the git repository:: - git tag -a 'v2.15' -m 'Tagged v2.15' - git push origin 'v2.15' + git tag -a 'v2.16' -m 'Tagged v2.16' + git push origin 'v2.16' diff --git a/pyproject.toml b/pyproject.toml index bdd8c11..a44cdde 100644 --- a/pyproject.toml +++ b/pyproject.toml @@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta" [project] name = "cso" -version = "2.15" +version = "2.16" authors = [ { name = "Arjo Segers" }, { name = "Lewis Blake" }, -- GitLab