fix(xtask): Pass --no-confirm to cargo-release (#162)

This fixes a bug where the `release` task would try to prompt the user
to confirm, and then fail (without rollback happening) because it's
actually running in a non-interactive context.

This _does_ mean that when `--execute` is passed, it will really
publish a new version! So take care.

Signed-off-by: Andrew Lilley Brinker <alilleybrinker@gmail.com>

Author: alilleybrinker

xtask/src/release.rs

@@ -345,15 +345,8 @@ impl Step for ReleaseCrate {
         let sh = Shell::new()?;
         let krate = self.krate.name();
         let bump = self.bump.to_string();
-        let execute = self.execute.then_some("--execute");
-
-        // TODO(alilleybrinker): It currently looks like this fails on networks
-        //                       which substitute in their own certificates,
-        //                       because Cargo is unable to validate the certificate.
-        //                       I believe this is because of how `xshell` isolates
-        //                       commands, which may be causing Cargo _not_ to pickup
-        //                       relevant configuration which would otherwise enable
-        //                       it to work on such a network.
+        let execute = self.execute.then_some("--execute --no-confirm");
+
         cmd!(
             sh,
             "cargo release -p {krate} --allow-branch main {execute...} {bump}"