Release build flow

[colfax23]

Need to establish a flow for building release executables, etc. Dependent on #7.

[remyroy]

Here is what it should look like:

Before building on each OS:

• Modify package.json to set the correct version number in the version field.
• Commit this new change to git.
• Add a git tag with the current version: git tag -a v1.4.0
• Might need to push the tag to remote: git push origin v1.4.0
• Push everything on the main branch of https://github.com/stake-house/wagyu-key-gen .

Using the correct machine for each OS (Ubuntu 18.04, Windows 10, macOS 10.15) and assuming all the dev tools are present:

• Make sure your OS is updated with the latest version/patches/updates. Reboot if needed.
• Fetch upstream: git fetch
• Switch to tag: git checkout v0.9.0
• Check for missing packages with yarn: yarn install
• Rebuild the app: yarn build
• Rebuild the packaged eth2deposit_proxy: yarn buildcli or yarn buildcliwin
• Rebuild the packaged Electron app for distribution: yarn dist
• Create a checksum file for the packaged Electron app for distribution:

pushd dist/
sha256sum 'Wagyu Key Gen-0.8.0.AppImage' > 'Wagyu Key Gen-0.8.0.AppImage.sha256'
popd

Can also use certUtil -hashfile C:\file.img SHA256 on Windows.

• Create a PGP signature file for the packaged Electron app for distribution:

pushd dist/
gpg --default-key E4BD8F0BA028F8816C9A5599B828200C4DDFCB11 --sign --armor --output 'Wagyu Key Gen-0.8.0.AppImage.asc' --detach-sig 'Wagyu Key Gen-0.8.0.AppImage'
popd

For each OS, add the following assets to the release on Github:

• The packaged Electron app for distribution.
• The corresponding .sha256 file.
• The corresponding .asc file.

Publish the new release on Github.