[bpapaspyros]

What and why

Releases were cut from a dispatch with GitHub's generated notes and no changelog. They now go through the changelog release workflows in ci-workflows, the same way ci-workflows releases itself: a dispatch opens a release pull request with the next version's section in CHANGELOG.rst, and its merge tags v<version> and moves v1.

• .github/workflows/release.yml is removed.
• .github/workflows/self-release.yml (new):
  • on a dispatch, reusable_prepare_changelog_release.yml opens the release pull request. The bump is derived from the commits, and bump overrides it;
  • when that pull request merges, reusable_changelog_release_tag.yml tags it.
• CHANGELOG.rst (new): the releases from 1.0.0 to 1.8.0, one section per tag, from the commits between them. 1.4.0 was tagged on the same commit as 1.3.0, so it reads "No changes."

Testing

• CHANGELOG.rst parses the way the release check and bloom read it.
• This has not run on GitHub yet.
• Tests updated, or not applicable
• Docs updated, or not applicable
• This changes or removes something existing (if so, title needs ! and means the next release is a major version bump)

Notes

• Merge after the next ci-workflows release. reusable_prepare_changelog_release.yml and reusable_changelog_release_tag.yml are not in its v1 yet, and from that release the release check takes sections for already-tagged versions as history.
• Releasing then takes the release App's secrets, passed with secrets: inherit.