e Prepare for next release

Co-Authored-By: Llewellyn Falco <[email protected]>

Author: claremacrae

build/HowToRelease.md

@@ -18,13 +18,13 @@ Creating the Build
 
 Publishing
 
-- [ ] Change version number to current version number, and new version number to `$UNSET_VERSION`
 - [ ] Commit and push `ApprovalTests.cpp`
 - [ ] Finish off the upload to github, by uploading the new .hpp, pasting in the release notes, and hitting "Publish release"
 - [ ] Finish off the release Tweet
 - [ ] Close any [Issues](https://github.com/approvals/ApprovalTests.cpp/issues) that were resolved in this release
 
 Prepare for next release
 
+- [ ] Change version number to current version number, and new version number to `$UNSET_VERSION`
 - [ ] Make sure the release notes named with the new version exist
 - [ ] `cp relnotes_template.md relnotes_X.X.X.md`

build/build_hpp.sh

@@ -7,8 +7,8 @@ set -o pipefail
 # Constants
 UNSET_VERSION="v.X.X.X"
 
-LAST_VERSION="v.5.1.0"
-VERSION="v.6.0.0"
+LAST_VERSION="v.6.0.0"
+VERSION=$UNSET_VERSION
 
 PUSH_TO_PRODUCTION="true"
 # Note that we won't push if the version number is unset