Release procedure

[Anaminus]

1. Clean up the imperative section of the change log.
   • Reorder changes based on interest.
   • Linkify things that can be.
   • Note that, on release, instances of imperative within the section (including links) will be replaced by the released version tag (e.g. v0.6.2).
2. Check for new versions of actions.
   • actions/checkout (v3)
   • actions/download-artifact (v3)
   • actions/setup-go (v3)
   • actions/upload-artifact (v3)
   • softprops/action-gh-release (v1)
3. Ensure that target Go version is present in actions/go-versions.
   • Otherwise, force version by updating GOVERSION.
4. Check that the GOVERSION environment variable in release.yml and test.yml supports the version in go.mod.
5. Run the release tool.
   • In the repo root, run go run _tools/version.go +minor, or whatever needed to increment version:
     • +major increments the major version (vX.0.0).
     • +minor increments the minor version (v0.X.0).
     • +patch increments the patch version (v0.0.X).
6. Verify that the release commit is correct.
7. Push the release commit to trigger the test workflow.
8. Wait for the test workflow to finish successfully.
   • Check that "Set up Go" job used target Go version.
9. Push the release tag to trigger the release workflow.
10. Wait for the release workflow to finish successfully.
11. Verify and publish the generated release draft.
12. Update DevForum post.
13. Have a proverbial beer.