Update release checklist

.github/content/release-checklist.md

@@ -15,6 +15,7 @@
 [mint a release]: https://github.com/PlasmaPy/PlasmaPy/actions/workflows/mint-release.yml
 [publish to PyPI]: https://github.com/PlasmaPy/PlasmaPy/blob/main/.github/workflows/publish-to-pypi.yml
 [release checklist]: https://github.com/PlasmaPy/PlasmaPy/tree/main/.github/content/release-checklist.md
+[release history]: https://pypi.org/project/plasmapy/#history
 [tests]: https://github.com/PlasmaPy/PlasmaPy/actions/workflows/tests.yml
 [Update pinned requirements]: https://github.com/PlasmaPy/PlasmaPy/actions/workflows/update-pinned-reqs.yml
 [weekly tests]: https://github.com/PlasmaPy/PlasmaPy/actions/workflows/weekly-tests.yml
@@ -53,8 +54,14 @@ This issue contains the procedure for releasing a new version of PlasmaPy.
 
  - [ ] Begin an upload to [Zenodo] for the new release using the `[email protected]` login, and reserve a DOI.
  - [ ] Run the GitHub Action to [mint a release]. Specify the version (i.e., `2024.5.0` or `2024.5.0rc1` for a release candidate) and copy/paste the reserved DOI from Zenodo. This action will update the DOI, build the changelog, and tag the release.
- - [ ] [Create a release on GitHub]. Choose the newly created tag (e.g., `v2024.5.0`) and use it as the title. Select the options to automatically generate release notes and create a discussion for the release. For beta releases or release candidates (e.g., `v2024.5.0rc1`), specify it as a pre-release. [TODO: specify which branch!]
- - [ ] Download a `.tar.gz` file of the tagged release from the [list of tagged versions] and upload it to [Zenodo].
+ - [ ] [Create a release on GitHub].
+ - Choose the newly created tag (e.g., `v2024.5.0`), and use it as the title. (The release will be performed from the tag, so it is not necessary to select the branch.)
+ - Select the option to automatically generate release notes.
+ - Select the option to create a discussion for the release under the _General_ category.
+ - For official releases, make sure the checkbox is selected for _Set as the latest release_. For beta releases or release candidates (e.g., `v2024.5.0rc1`), specify it as a pre-release.
+ - Click on _Publish release_, which will create the GitHub release and trigger the GitHub workflow to [publish to PyPI].
+ - Check the [release history] on PyPI to make sure that the release was successful.
+ - [ ] Download a `.tar.gz` file of the tagged release from the [list of tagged versions] on GitHub, and upload it to [Zenodo].
  - [ ] Update the author list with new authors from the automatically generated release notes or [`CITATION.cff`].
  - [ ] Update the bibliography, and publish the release to Zenodo.
  - [ ] Create and merge a pull request from the release branch back into `main`. <!-- Automate pull request creation? Change it into a commit? -->