chore: version bump (#37)

Trigger release on merge to main branch.

Issue: #20

Author: Joris Conijn

.github/workflows/release.yml

@@ -1,8 +1,8 @@
 name: Create Release
 on:
   push:
-    tags:
-      - 'v*'
+    branches:
+      - main
 
 jobs:
   build:
@@ -35,6 +35,9 @@ jobs:
           release_name: Release v${{ steps.vars.outputs.version }}
           draft: false
           prerelease: false
+      - uses: release-drafter/release-drafter@v5
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
       - name: Upload Release Asset
         id: upload-release-asset
         uses: actions/upload-release-asset@v1

CONTRIBUTING.md

@@ -16,22 +16,10 @@ reported the issue. Please try to include as much information as you can.
 
 ## Releases
 
-First you will need to update the `version` in the [`pyproject.toml`](./pyproject.toml) file. Next you need to merge the
-change to the `develop` branch using a pull request.
+First you will need to update the `version` in the [`pyproject.toml`](./pyproject.toml) file.
+Next you need to merge these changes into the `develop` branch using a pull request.
 
-Lookup the generated release notes, they are listed as draft. Copy them to a temporary file for later use.
-
-Then you need to create a new release. You can do this by creating a tag and push it to the remote:
-
-```bash
-git tag v$(awk '/version/{print $NF}'  pyproject.toml | sed 's/\"//g')
-git push --tags
-```
-
-This will trigger the GitHub Actions [`release`](.github/workflows/release.yml) workflow. When the release process is
-done. You need to create a pull request from `develop` to `main` and merge it.
-
-Then you need to the releases section on GitHub and update the new release. Go to the releases section on GitHub and
-update the new release with the previously stored release notes.
+You need to create a pull request from `develop` to `main` and merge it. This will trigger the GitHub Actions [`release`](.github/workflows/release.yml)
+workflow.
 
 All done!