Use release drafter to publish new releases easily

[Joonalai]

Expected behaviour Release drafter could be adopted in the project to make it easier to publish new releases.

Current behaviour Publishing releases require lot of manual work.

Describe alternatives you've considered Continue using the current release progress.

Additional context Here are some files that I have been drafting for this.

Contents of .github/workflows/release-drafter.yml ```yml name: Release Drafter on: push: branches: - main # pull_request event is required only for autolabeler pull_request: types: [opened, reopened, synchronize] permissions: contents: read jobs: update_release_draft: permissions: # write permission is required to create a github release contents: write # write permission is required for autolabeler # otherwise, read permission is required at least pull-requests: write runs-on: ubuntu-latest steps: # Drafts your next Release notes as Pull Requests are merged into "master" - uses: release-drafter/release-drafter@v6 # (Optional) specify config name to use, relative to .github/. Default: release-drafter.yml # with: # config-name: my-config.yml # disable-autolabeler: true env: GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} ``` Contents of .github/release-drafter.yml ```yml name-template: 'v$RESOLVED_VERSION' tag-template: 'v$RESOLVED_VERSION' version-resolver: major: labels: - 'major' minor: labels: - 'minor' patch: labels: - 'patch' default: patch template: | ## Changes $CHANGES ```

[Joonalai]

@LKajan I think it would be easier for you to implement this since you have push right to the repository and can thus experiment with this more easily.