Automate releases

[CharlieKarafotias]

Current release process

1. Open PR
2. Review on GitHub
3. Merge to main
4. Go back to terminal and build release cargo build -r
5. Create release on GitHub following convention vx.x.x. For example, 2.0.0 has tag v2.0.0. Attach release binary to this as well.
6. Publish release

Proposed release process

1. Open PR
2. Review and merge PR locally
3. On merge to main, run the commands cargo build -r && gh release create [<tag>] [<files>...]

Resources:

• GH CLI
• Look into pre-commit setup and figure out way to do this on merge to master
  • Run hooks at certain stages
  • Looks like we want after a git merge where target is main branch (if possible... i cant tell). See here
  • Git docs for post-merge githook. Look for examples of merge to main.

Questions to figure out:

• When a new person works on project, how to ensure they are set up to perform release?
• Should there be an onboarding/contributing section for GH?
• Would it be easier to use github actions for this? What costs are associated with this?

[CharlieKarafotias]

Still need to merge to main and fix automation. Getting error:

github-release...........................................................Failed
- hook id: github-release
- duration: 0s
- exit code: 1

Executable `version=$(./target/release/tmgr` not found

• Is there a different way to get the tag?
• Why would the executable not be found?