Prepare release 0.9.0

doc/changes/changelog.md

@@ -1,6 +1,7 @@
 # 📝 Changes
 
 * [unreleased](unreleased.md)
+* [0.9.0](changes_0.9.0.md)
 * [0.8.0](changes_0.8.0.md)
 * [0.7.0](changes_0.7.0.md)
 * [0.6.2](changes_0.6.2.md)
@@ -17,6 +18,7 @@
 hidden:
 ---
 unreleased
+changes_0.9.0
 changes_0.8.0
 changes_0.7.0
 changes_0.6.2

doc/changes/changes_0.9.0.md

@@ -0,0 +1,56 @@
+# 0.9.0 - 2024-05-08
+
+## 🚨 Breaking Changes
+* **CI-CD Workflow (Breaking Change)**
+
+    **Overview:**
+
+    The CI-CD workflow now assumes the changelog to be in markdown and the location `/doc/changes/change_x.y.z.md`
+
+## 🐞 Fixed
+* Fixed `_deny_filter` function in `exasol.toolbox._shared` module
+* Fixed GitHub workflow references in `ci.yml`, ci-cd.yml` and `pr-merge.yml` workflows
+* Fixed indent error/issue in `checks.yml` workflow
+
+## ✨ Added
+* **Added Nox Task `prepare-release`**
+
+    **Overview:**
+
+    A new Nox task, `prepare-release`, has been introduced to streamline the release preparation process. This task automates several crucial steps:
+
+    - Create a dedicated branch for the release changes.
+    - Transfer changes from the "Unreleased" section to the appropriate versioned changelog section.
+    - Update the version number to the next release.
+    - Initiate a Pull Request (PR) for review and integration into the main branch.
+
+    **Usage:**
+
+    To prepare a release, simply execute a command in your terminal like in the example below:
+
+    ```shell
+    nox -s prepare-release -- 1.10.1
+    ```
+
+    Add the changes for releasing on top of the current branch:
+
+    ```shell
+    nox -s prepare-release -- 1.10.1 --no-pr --no-branch
+    ```
+
+    For additional options and help regarding the task `prepare-release`, execute:
+
+    ```shell
+    nox -s prepare-release -- -h 
+    ```
+
+* **Added Plugin Support for Nox Task `prepare-release`**
+
+    - For further details on the plugin specification, refer to `exasol.toolbox.nox.plugin`.
+    - For an example of usage, refer to the `noxconfig` of the Python toolbox.
+
+## 📚 Documentation
+* Fixed typos and updated documentation
+
+## 🔩 Internal
+* Restructured `exasol.toolbox.nox` module

doc/changes/unreleased.md

@@ -1,56 +1 @@
 # Unreleased
-
-## 🚨 Breaking Changes
-* **CI-CD Workflow (Breaking Change)**
-
-    **Overview:**
-
-    The CI-CD workflow now assumes the changelog to be in markdown and the location `/doc/changes/change_x.y.z.md`
-
-## 🐞 Fixed
-* Fixed `_deny_filter` function in `exasol.toolbox._shared` module
-* Fixed GitHub workflow references in `ci.yml`, ci-cd.yml` and `pr-merge.yml` workflows
-* Fixed indent error/issue in `checks.yml` workflow
-
-## ✨ Added
-* **Added Nox Task `prepare-release`**
-
-    **Overview:**
-
-    A new Nox task, `prepare-release`, has been introduced to streamline the release preparation process. This task automates several crucial steps:
-
-    - Create a dedicated branch for the release changes.
-    - Transfer changes from the "Unreleased" section to the appropriate versioned changelog section.
-    - Update the version number to the next release.
-    - Initiate a Pull Request (PR) for review and integration into the main branch.
-
-    **Usage:**
-
-    To prepare a release, simply execute a command in your terminal like in the example below:
-
-    ```shell
-    nox -s prepare-release -- 1.10.1
-    ```
-
-    Add the changes for releasing on top of the current branch:
-
-    ```shell
-    nox -s prepare-release -- 1.10.1 --no-pr --no-branch
-    ```
-
-    For additional options and help regarding the task `prepare-release`, execute:
-
-    ```shell
-    nox -s prepare-release -- -h 
-    ```
-
-* **Added Plugin Support for Nox Task `prepare-release`**
-
-    - For further details on the plugin specification, refer to `exasol.toolbox.nox.plugin`.
-    - For an example of usage, refer to the `noxconfig` of the Python toolbox.
-
-## 📚 Documentation
-* Fixed typos and updated documentation
-
-## 🔩 Internal
-* Restructured `exasol.toolbox.nox` module

exasol/toolbox/templates/github/workflows/build-and-publish.yml

@@ -17,7 +17,7 @@ jobs:
         uses: actions/checkout@v3
 
       - name: Setup Python & Poetry Environment
-        uses: exasol/python-toolbox/.github/actions/python-environment@0.8.0
+        uses: exasol/python-toolbox/.github/actions/python-environment@0.9.0
 
       - name: Build Artifacts
         run: poetry build

exasol/toolbox/templates/github/workflows/check-release-tag.yml

@@ -14,7 +14,7 @@ jobs:
         uses: actions/checkout@v3
 
       - name: Setup Python & Poetry Environment
-        uses: exasol/python-toolbox/.github/actions/python-environment@0.8.0
+        uses: exasol/python-toolbox/.github/actions/python-environment@0.9.0
 
       - name: Check Tag Version
         # make sure the pushed/created tag matched the project version

exasol/toolbox/templates/github/workflows/checks.yml

@@ -15,7 +15,7 @@ jobs:
           fetch-depth: 0
 
       - name: Setup Python & Poetry Environment
-        uses: exasol/python-toolbox/.github/actions/python-environment@0.8.0
+        uses: exasol/python-toolbox/.github/actions/python-environment@0.9.0
 
       - name: Check Version(s)
         run: poetry run version-check  <<Add path to version.py file>> 
@@ -30,7 +30,7 @@ jobs:
         uses: actions/checkout@v3
 
       - name: Setup Python & Poetry Environment
-        uses: exasol/python-toolbox/.github/actions/python-environment@0.8.0
+        uses: exasol/python-toolbox/.github/actions/python-environment@0.9.0
 
       - name: Build Documentation
         run: |
@@ -50,7 +50,7 @@ jobs:
         uses: actions/checkout@v3
 
       - name: Setup Python & Poetry Environment
-        uses: exasol/python-toolbox/.github/actions/python-environment@0.8.0
+        uses: exasol/python-toolbox/.github/actions/python-environment@0.9.0
         with:
           python-version: ${{ matrix.python-version }}
 
@@ -71,7 +71,7 @@ jobs:
         uses: actions/checkout@v3
 
       - name: Setup Python & Poetry Environment
-        uses: exasol/python-toolbox/.github/actions/python-environment@0.8.0
+        uses: exasol/python-toolbox/.github/actions/python-environment@0.9.0
         with:
           python-version: ${{ matrix.python-version }}
 
@@ -93,7 +93,7 @@ jobs:
         uses: actions/checkout@v3
 
       - name: Setup Python & Poetry Environment
-        uses: exasol/python-toolbox/.github/actions/python-environment@0.8.0
+        uses: exasol/python-toolbox/.github/actions/python-environment@0.9.0
         with:
           python-version: ${{ matrix.python-version }}
 

exasol/toolbox/templates/github/workflows/gh-pages.yml

@@ -12,7 +12,7 @@ jobs:
         uses: actions/checkout@v3
 
       - name: Setup Python & Poetry Environment
-        uses: exasol/python-toolbox/.github/actions/python-environment@0.8.0
+        uses: exasol/python-toolbox/.github/actions/python-environment@0.9.0
 
       - name: Build Documentation
         run: |

exasol/toolbox/templates/github/workflows/report.yml

@@ -21,7 +21,7 @@ jobs:
           fetch-depth: 0
 
       - name: Setup Python & Poetry Environment
-        uses: exasol/python-toolbox/.github/actions/python-environment@0.8.0
+        uses: exasol/python-toolbox/.github/actions/python-environment@0.9.0
 
       - name: Download Artifacts
         uses: actions/download-artifact@v3

exasol/toolbox/version.py

@@ -5,6 +5,6 @@
 # Do not edit this file manually!
 # If you need to change the version, do so in the project.toml, e.g. by using `poetry version X.Y.Z`.
 MAJOR = 0
-MINOR = 8
+MINOR = 9
 PATCH = 0
 VERSION = f"{MAJOR}.{MINOR}.{PATCH}"

pyproject.toml

@@ -3,7 +3,7 @@ name = "exasol-toolbox"
 packages = [
     { include = "exasol" },
 ]
-version = "0.8.0"
+version = "0.9.0"
 description = ""
 authors = [
     "Nicola Coretti <[email protected]>"