Currently, to do releases we have to:

1. bump the version number in Cargo.toml to x.y.z and apply changesets cargo xtask changelog --release vx.y.z. cargo release x.y.z --execute
2. Create and merge the pr
3. Create and push tag vx.y.z on that merge commit from bors when merged.

I'd like to streamline this process to only two steps

1. cargo release x.y.z --execute
2. submit pr and merge
3. ???
4. profit!! (CI creates tag and eventually publishes to crates.io)

There is also an issue with releasing versions behind origin:main, this could be improved by allowing the same process for those changes, ie:

1. Create branch vx.y.z based on the most adjacent tag. Publish this branch (this shouldn't trigger ci)
2. cargo release --execute x.y.z
3. submit pr to merge changes into x.y.z and merge
4. ci creates tag and eventually publishes to crates.io

This process doesn't work today, because the ci for publishing is only triggered on published tags.

Github doesn't allow the default github token in workflows to trigger other workflows except for workflows on workflow_dispatch and repository_dispatch, to circumvent this, it's possible to use a deploy key (which I've already added to this repo, secrets.COMMIT_KEY)