Changed the publish release part of the instructions

UCREL · Jan 18, 2022 · 9283107 · 9283107
1 parent fea9510
commit 9283107
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 3 deletions.
diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -5,7 +5,7 @@ All notable changes to this project will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
-## [Unreleased]
+## Unreleased
 
 ## [v0.2.0](https://github.com/UCREL/pymusas/releases/tag/v0.2.0) - 2022-01-18
 

diff --git a/RELEASE_PROCESS.md b/RELEASE_PROCESS.md
@@ -53,13 +53,13 @@ For more information about CITATION.cff files see the [Citation File Format webs
     git tag -s $TAG && git push origin main --tags
     ```
 
-8. Find the tag you just pushed [on GitHub](https://github.com/UCREL/pymusas/tags), click edit, then copy over the output of:
+8. Find the tag you just pushed [on GitHub](https://github.com/UCREL/pymusas/tags), click the "..." to the right of the "Verified" badge, and then click "Create release". Set the title of the release to "v{VERSION}" and copy the output from the following script into the markdown text box:
 
     ```
     python scripts/release_notes.py
     ```
 
-9. Click "Publish Release". GitHub Actions will then handle the rest, including publishing the package to PyPI.
+9. Click "Publish release". GitHub Actions will then handle the rest, including publishing the package to PyPI.
 
 
 ## Fixing a failed release