Create a Release

Steps for publishing a new version, follow in order

Create a new tag, but make it prerelease (even if it's stable), will change it after we finished the release.
Run the build_linux.groovy jenkinsfile.
Upload the new linux builds to the new release (on github).
Update the AUR with the new Arch PKGBUILDs.
Run the build_test_pkgbuilds.groovy jenkinsfile to test the AUR Pkg.
Upload the pkg.tar.zst arch pkg generated by the above jenkins job to the releases.

Create a macos releases folder.
Build the project (cargo build --release).
Copy the built bin to the releases folder, change name from estash to estash-macos.
Add the bin to the .app template (with the estash name in the macos folder).
Change the version in the .plist file in the .app template
Copy the .app folder to the releases folder.
Compress .app folder into .tar.gz (with the name estash-macos-app.tar.gz).
Make dmg from the .app folder using the make-dmg.sh script, remove the .app folder.
Upload all the files inside the macos releases folder to the github release.
Run the build_homebrew.groovy jenkinsfile.
Update estash brew formula in the tap repo & upload the archive to the github release.

Make a builds folder.
Compile project (cargo build --release).
Use resource hacker to add the logo to the exe (the .ico file).
Copy bin to builds folder.
Make an exe installer by changing the placeholder for the version from the inno file to the new version.
Copy exe installer to builds.
Upload builds to the github release.