Feature/#203 integrated txaie (#204)

* #203: Integrated official TXAIE release
* Updated test
* Added additional progress messages
* Removed Python versions other than 3.10 from build matrix
* Ignored pylint errors for imports from Cython-compiled text-ai-extension
* Activated more extensive test
* Hide animated spinner in CI
* Prepare release 0.6.0

Co-authored-by: Torsten Kilias <[email protected]>

Author: ckunki

.github/workflows/merge-gate.yml

@@ -43,7 +43,7 @@ jobs:
 
       - name: Allow unprivileged user namespaces
         run: |
-          sudo sysctl -w kernel.apparmor_restrict_unprivileged_userns=0      
+          sudo sysctl -w kernel.apparmor_restrict_unprivileged_userns=0
 
       - name: Tests
         env:
@@ -89,12 +89,13 @@ jobs:
 
       - name: Allow unprivileged user namespaces
         run: |
-          sudo sysctl -w kernel.apparmor_restrict_unprivileged_userns=0      
+          sudo sysctl -w kernel.apparmor_restrict_unprivileged_userns=0
 
       - name: Tests
         env:
           TXAIE_PRE_RELEASE_URL: ${{ vars.ZIP_URL }}
           TXAIE_PRE_RELEASE_PASSWORD: ${{ secrets.ZIP_PASSWORD }}
+          INTERACTIVE: False # hide animated spinner in CI
         run: poetry run -- pytest -rA --setup-show test/integration/test_text_ai_extension_wrapper.py
 
   # This job ensures inputs have been executed successfully.
@@ -104,7 +105,8 @@ jobs:
     permissions:
       contents: read
     # If you need additional jobs to be part of the merge gate, add them below
-    needs: [ fast-checks, saas-tests, large-runner-tests ]
+    # Removed saas-tests from being required
+    needs: [ fast-checks, large-runner-tests ]
 
     # Each job requires a step, so we added this dummy step.
     steps:

.gitignore

@@ -7,4 +7,5 @@ __pycache__/
 /.lint.json
 /.lint.txt
 /.html-documentation/
-.build_output
+/.security.json
+.build_output

doc/changes/changelog.md

@@ -0,0 +1,13 @@
+# 0.6.0 - 2025-07-17
+
+## Features
+
+* #203: Integrated official TXAIE release
+
+## Bugfix
+
+* #182: Updated `LATEST_KNOWN_VERSION` to be dynamically fetched with `importlib.metadata` for `transformers_extension_wrapper` and `sagemaker_extension_wrapper`.
+
+## Refactorings
+
+* Relocked poetry dependencies to resolve CVE-2025-47287 and CVE-2025-47273

doc/changes/changes_0.6.0.md

@@ -1,8 +1 @@
 # Unreleased
-
-## Bugfix
-* #182: Updated LATEST_KNOWN_VERSION to be dynamically fetched with importlib.metadata for
-transformers_extension_wrapper & sagemaker_extension_wrapper
-
-## Internal
-* Relocked poetry dependencies to resolve CVE-2025-47287 and CVE-2025-47273

doc/changes/unreleased.md

@@ -2,74 +2,18 @@
 
 ## How to Release?
 
-Creating a new release of the NC requires 4 steps
+Creating a new release of the NC requires 3 steps
 
-1. [Prepare the release](#prepare-the-release)
+1. Prepare the release
 2. Merge your pull request to the default branch
-3. [Switch to main branch and update it from remote](#switching-to-the-default-branch)
-4. [Create and push a tag to GitHub](#creating-a-git-tag-and-pushing-it-to-github)
-
-### Prepare the Release
-
-```shell
-poetry run -- nox -s release:prepare -- <additional-options> <version>
-```
-
-`<additional-options>` include
-* `--no-branch` if already working on a branch
-* `--no-pr` if you already created a pull request or plan to do so manually after preparing the release
-
-The command uses the nox task `project:fix` of the [Python Tool
-Box](https://github.com/exasol/python-toolbox/) (PTB) and
-* Optionally creates a branch
-* Optionally creates a pull request
-* Updates the [version number](#updating-the-version-number-without-preparing-a-release) and the Change Log
-
-Updating the Change Log includes
-* Moving file `doc/changes/unreleased.md` to a filename reflecting the specified version, e.g. `doc/changes/changes_1.2.3.md`
-* Updating the list of changes files in `doc/changes/changelog.md`
-* Adding the current date at the top of the changelog as the date of the release
-* Creating a new file `doc/changes/unreleased.md`
-
-### Switching to the default Branch
-
-You can find out the default branch with
+3. Trigger the release process
 
 ```shell
-git remote show origin | sed -n '/HEAD branch/s/.*: //p'
+poetry run -- nox -s release:prepare -- --type {major,minor,patch} <additional-options>
+poetry run -- nox -s release:trigger
 ```
 
-The following commands switches to branch `main` and updates it from remote
-
-```shell
-git checkout main
-git pull
-```
-
-### Creating a Git Tag and Pushing it to GitHub
-
-Use the following commands to create a Git Tag and push it to GitHub:
-
-```shell
-TAG=<version>
-git tag "$TAG"
-git push origin "$TAG"
-```
-
-Pushing the new tag to GitHub will trigger GitHub workflow `ci-cd.yml`.
-
-The workflow completely automates the release process, incl.
-* Creating a release on GitHub and
-* Publishing the release to [PyPi](https://pypi.org/)
-
-## Updating the Version Number Without Preparing a Release
-
-You can use the following commands to manually update the version number without preparing a release:
-
-1. Update version in file `pyproject.toml` or call `poetry version <version>`
-2. Call `poetry run -- version-check version.py --fix`
-
-The second command will update the version number in file `version.py`.
+For further information, please refer to section [How to Release](https://exasol.github.io/python-toolbox/main/user_guide/how_to_release.html) in the PTB's User Guide.
 
 ## Selecting the Versions for SLCT and SLCR