From a73a0f14f18cec3233b47fa8983de85596318ac3 Mon Sep 17 00:00:00 2001 From: Dave Grote Date: Tue, 5 Sep 2023 08:44:02 -0700 Subject: [PATCH] Release 0.27.0 --- PICMI_Python/README.md | 4 ++-- PICMI_Python/version.py | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/PICMI_Python/README.md b/PICMI_Python/README.md index df93eee..2623e7e 100644 --- a/PICMI_Python/README.md +++ b/PICMI_Python/README.md @@ -36,7 +36,7 @@ be updated. The update has several steps, updating the version number, adding a of PyPI. Currently, the version number is modified by hand by modifying the number in the `version.py` file, incrementing the second -number, the minor release version. After changing the file, make a commit with the change with a comment like "Release 0.22.0", +number, the minor release version. After changing the file, make a commit with the change with a comment like "Release 0.27.0", updating the version number of course. Please don't make any other changes in the commit. Note that it is ok to push a version update directly to the main branch assuming it has been approved. @@ -44,7 +44,7 @@ it has been approved. Next, add a tag and push the changes to the repo: ``` - git tag -a 0.22.0 -m "Release 0.22.0" + git tag -a 0.27.0 -m "Release 0.27.0" git push origin git push origin --tags ``` diff --git a/PICMI_Python/version.py b/PICMI_Python/version.py index 826d20e..cf7b6d6 100644 --- a/PICMI_Python/version.py +++ b/PICMI_Python/version.py @@ -1 +1 @@ -__version__ = '0.26.0' +__version__ = '0.27.0'