Release process

These are the steps to release a new build:

1. Run cargo release patch and see whether everything looks good.
2. Run cargo release patch --execute to actually cut a new release.
3. At this point a GitHub Workflow for the new git tag that was created by step 2 will be triggered. This workflow has various environmental gates that someone needs to approve. In particular, there is a first environment package that will sign everything and then create deployment packages for various platforms. Once that stage is finished, there are three environments that correspond to the three channels we have for Juliaup: the dev, release-preview and release channel. Ideally one should approve these in order, i.e. first approve the dev channel, wait until that is deployed, then the release-preview channel, wait until this is deployed, then the release channel.

Generally one should never create a tag manually, always use cargo release for that. You can enable the cargo release command by globally installing cargo-release with the command cargo install cargo-release.

I (David) am on on the dev channel with my machines. When I release a new version, I always put a pause between releasing the dev channel and the release-preview channel where I test that all my machines properly update and everything works.