ci: use cargo-release for publishing
#52
Conversation
|
We can remove the |
I think we will still want to use release-plz for aranya-core. |
|
@jdygert-spok is this PR still needed after our |
|
Yes, we still want something to do the publishing automatically. |
10a8946 to
e9be838
Compare
|
For the case where tag creation and crate publishing succeeds, but creating the github release fails, we may want to be able to continue triggering the publish.yml workflow to create a github release separately. A github tag/release can be deleted and recreated, but a Rust crate cannot be republished with the same version. I originally combined release.yml and publish.yml for simplicity. But I think keeping them separate will give us more flexibility to handle the event when things don't run perfectly during a release. |
|
Separated the workflows out again so we can manually trigger |
c5f0bb0
Rather than contorting
release-plzto work better for a single version and our workflow, usecargo-releasefor publishing.Process:
Cargo.tomlwithcargo release tag.cargo release tag.cargo release push.If there is an existing tag for the current version in
Cargo.toml, the release process will be skipped.Workflows tested on this fork:
gknopf-aranya#2