release: v1.0.3 (#1446)

.bumpversion.cfg

@@ -1,5 +1,5 @@
 [bumpversion]
-current_version = 1.0.2
+current_version = 1.0.3
 parse = (?P<major>\d+)\.(?P<minor>\d+)(\.(?P<patch>\d+))?
 serialize = 
 	{major}.{minor}.{patch}

CHANGELOG.md

@@ -2,6 +2,20 @@
 
 Notable changes to this project will be documented in this file. The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 
+## [1.0.3] - 2024-02-07
+
+### General
+
+- Support for Python 3.11 and updated dependencies
+
+### Testing
+
+- Testing of Jupyter notebooks in CI
+
+### Next
+
+See commit history.
+
 ## [1.0.2] - 2024-01-24
 
 ### Cartesian

docs/development/tools/release.md

@@ -17,10 +17,10 @@ Currently, GT4Py releases are published in PyPI (and TestPyPI) and also as commi
 4. Commit the changes with the following message:
 
    ```bash
-   $ git commit -m 'Releasing 0.{M}.{m}.{p} version.'
+   $ git commit -m 'Releasing {M}.{m}.{p} version.'
    ```
 
-5. On the GitHub website go to _Releases_ and _Draft a new release_. Choose `v0.{M}.{m}.{p}` as tag and select a branch (usually `main`). Follow the style of the previous releases for the title (`GT4Py v0.{M}.{m}.{p}`) and description. Then _Publish release_.
+5. On the GitHub website go to _Releases_ and _Draft a new release_. Choose `v{M}.{m}.{p}` as tag and select a branch (usually `main`). Follow the style of the previous releases for the title (`GT4Py v{M}.{m}.{p}`) and description. Then _Publish release_.
 
 6. Publishing the release will trigger a Github action to deploy to TestPyPI. Install the package from TestPyPi and do basic tests.
 

src/gt4py/__about__.py

@@ -33,5 +33,5 @@
 __license__: Final = "GPL-3.0-or-later"
 
 
-__version__: Final = "1.0.2"
+__version__: Final = "1.0.3"
 __version_info__: Final = pkg_version.parse(__version__)