Automate release tagging

[kdeldycke]

A release is created when maintainers creates a tag. It gets automatically packaged and distributed on PyPi.

This issue is about having a way for the tagging process to be even more automated.

Ideal workflow:

1. Have a draft GitHub release continuously updated against the main branch. This provides a great overview of what's going to be release next and allow to catch issues before cutting a release.

2. We then piggy-back on GitHub's release workflow: when maintainers decides to release a version, the trigger is the publishing of the pending draft GitHub release.

3. Release date is set in changelog.md. Comparison URL is updated. warning admonition is removed. A new release commit and tag is created and pushed to main. This automates the manual steps documented in the development page.

4. The published release is updated with latest changelog entries. Versions are checked to match.

5. the current build workflow picks up the git tag and finish the publishing process as usual.

[kdeldycke]

Things to evaluate:

• https://github.com/release-drafter/release-drafter
• https://github.com/christian-draeger/increment-semantic-version
• https://github.com/jessicalostinspace/cut-release-action
• https://github.com/WyriHaximus/github-action-next-semvers
• https://github.com/metcalfc/changelog-generator
• https://github.com/author/action-rollback
• https://github.com/twisted/towncrier
• https://pypi.org/project/githubrelease/
• https://pypi.org/project/autopub/

[kdeldycke]

All the workflow logic has been implemented ad-hoc in my https://github.com/kdeldycke/workflows project. Workflows there are reuseable. Trying to make them more robust and generic will allows for automatic release tagging here.

[kdeldycke]

Has been fixed since v4.9.1.

[github-actions[bot]]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.