diff --git a/.github/workflows/publish_pypi.yml b/.github/workflows/publish_pypi.yml
deleted file mode 100644
index d310101..0000000
--- a/.github/workflows/publish_pypi.yml
+++ /dev/null
@@ -1,21 +0,0 @@
-name: Publish python poetry package
-on:
-  # Triggers the workflow on push or pull request events but only for the "main" branch
-  push:
-    branches: [ "main" ]
-
-jobs:
-  build:
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@v3
-      - name: Build and publish to pypi
-        shell: bash
-        env:
-          PYPI_DB_ROCKET: ${{ secrets.PYPI_DB_ROCKET }}
-        run: |
-          pip install -r requirements.txt
-          python3 -m build --no-isolation
-          echo "Build successfull, uploading now..."
-          python3 -m twine upload dist/* -u "__token__" -p "$PYPI_DB_ROCKET" --skip-existing
-          echo "Upload successfull!"
\ No newline at end of file
diff --git a/.github/workflows/release-please.yml b/.github/workflows/release-please.yml
new file mode 100644
index 0000000..c63d931
--- /dev/null
+++ b/.github/workflows/release-please.yml
@@ -0,0 +1,38 @@
+on:
+  push:
+    branches:
+      - main
+
+permissions:
+  contents: write
+  pull-requests: write
+
+name: release-please
+
+jobs:
+  release-please:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: google-github-actions/release-please-action@v4.0.2
+        id: release
+        with:
+          # this assumes that you have created a personal access token
+          # (PAT) and configured it as a GitHub action secret named
+          # `MY_RELEASE_PLEASE_TOKEN` (this secret name is not important).
+          #token: ${{ secrets.MY_RELEASE_PLEASE_TOKEN }}  <-- Required to run GitHub Actions CI checks, lets try without.
+          # this is a built-in strategy in release-please, see "Action Inputs"
+          # for more options
+          release-type: python
+      - uses: actions/checkout@v3
+        if: ${{ steps.release.outputs.release_created }}  # Run only on release
+      - name: Build and publish to pypi
+        shell: bash
+        env:
+          PYPI_DB_ROCKET: ${{ secrets.PYPI_DB_ROCKET }}
+        run: |
+          pip install -r requirements.txt
+          python3 -m build --no-isolation
+          echo "Build successfull, uploading now..."
+          python3 -m twine upload dist/* -u "__token__" -p "$PYPI_DB_ROCKET" --skip-existing
+          echo "Upload successfull!"
+        if: ${{ steps.release.outputs.release_created }}  # Run only on release
\ No newline at end of file
diff --git a/pull_request_template.md b/pull_request_template.md
index c10ec9c..3c2abea 100644
--- a/pull_request_template.md
+++ b/pull_request_template.md
@@ -1,9 +1,14 @@
 <!--
-For Work In Progress Pull Requests, please use the Draft PR feature, see https://github.blog/2019-02-14-introducing-draft-pull-requests/ for further details.
+🚨 IMPORTANT: Please format your **PR title** in the following format:
+    - `feat: JIRA_TICKET_ID DESCRIPTIVE_SUMMARY_OF_CHANGES` -> minor version bump (v1.2.3 -> v1.3.0)
+    - `fix: JIRA_TICKET_ID DESCRIPTIVE_SUMMARY_OF_CHANGES` -> patch version bump (v1.2.3 -> v1.2.4)
+    - `feat!: JIRA_TICKET_ID DESCRIPTIVE_SUMMARY_OF_CHANGES` -> major version bump (v1.2.3 -> v2.0.0)
 
-Please ensure your pull request title uses following pattern:
- - JIRA_TICKET_ID DESCRIPTIVE_SUMMARY_OF_CHANGES 
- - Example: RR-2582 Remove All Bugs From Service
+    - Example: `feat: RR-2582 Remove All Bugs From Service`
+
+This ensures that the release-please action can create a new version tag and changelog entries for you.
+
+---
 
 Please ensure you've done the following:  
   - 👷‍♀️ Create small PRs. In most cases, this will be possible. If your PR is large, try to split it in order to make it more readable.