cargo-workspaces
cargo-workspaces copied to clipboard
Publish should not leave the repository dirty on failure
Related to #12, cargo-ws
shouldn't leave a project in a half released state if there are failures during publishing. Currently cargo-ws
will leave the repository in whatever state it got up to, which means that I have to manually undo those changes first before I can retry. Examples of this include committing changes when a tag already exists, or committing and tagging releases when cargo-publish
fails.