Release drafter update attempt #2

[JuanPedroGHM]

Due Diligence

• General:
  • [ ] title of the PR is suitable to appear in the Release Notes
• Implementation:
  • [ ] unit tests: all split configurations tested
  • [ ] unit tests: multiple dtypes tested
  • [ ] benchmarks: created for new functionality
  • [ ] benchmarks: performance improved or maintained
  • [ ] documentation updated where needed

Description

Update to the configuration. This will not work properly on the next release, but as long as we stay on the same release branch, this should be fine. We could stick with our current branching strategy, but every time we create a new release branch, it will cause some trouble.

This also includes some auto-labeling functionality.

Issue/s resolved: #

Changes proposed:

• Workflow changes to releases drafter

Does this change modify the behaviour of other functions? If so, which?

no