This makes sense when the crate/Cargo.toml version isn't bumped. In this case, the 0.7.1 crate already exists -- and indeed, we don't want to publish over it.
However, this failure causes the CI run to ultimately error out.
Do we want to gate the crate publishing logic to only run on git tag/GH release events?
Noticed that the crate publishing task fails on merges to main: https://github.com/deislabs/bindle/runs/5012836836?check_suite_focus=true
This makes sense when the crate/Cargo.toml version isn't bumped. In this case, the 0.7.1 crate already exists -- and indeed, we don't want to publish over it.
However, this failure causes the CI run to ultimately error out.
Do we want to gate the crate publishing logic to only run on git tag/GH release events?