Once substrace can be installed through cargo and is fixed up and stable, we want to publish it as a package on crates.io. Preferably we use CI for this, meaning we want a workflow that is run on a push to the release-vx.y.z branch; and publishes to crates.io after running checks etc. We'll store the crates.io credentials in the github secrets.
Needs #3 and #5.
Once substrace can be installed through cargo and is fixed up and stable, we want to publish it as a package on crates.io. Preferably we use CI for this, meaning we want a workflow that is run on a push to the
release-vx.y.zbranch; and publishes to crates.io after running checks etc. We'll store the crates.io credentials in the github secrets.