cargo publish --workspace should fail early if you don't have permission to publish everything

[jneem]

Problem

It's possible to have crates.io ownership on some -- but not all -- crates in a workspace. In that case, cargo publish --workspace might publish a few crates before trying to publish one that isn't allowed and failing.

Proposed Solution

cargo publish --workspace should check that it has publish permissions on all the crates that it wants to publish before it publishes any of them. Alternatively, it should be able to publish them all at once, atomically.

Notes

No response

[epage]

(as jneem implemented workspace publishing, they will be familiar with most of this but including it for completeless / other people)

I believe both of these would require new protocol support with some provision to not break publishing to alternative registries.

Atomic support was recognized as a potential future step when workspace publishing was stabilized (#15636).

Other issues with how publish happens

• Expand manifest validation for all settings #4377
• When crates.io gives 429, cargo should back off and retry later #13530
• Provide a way to programmatically check registry credentials #16071
• on cargo publish, check for verified email before compiling #8221
• Add a dry-run publish API crates.io#4329

The meta issue for all of this is rust-lang/crates-io-cargo-teams#82

One interesting question is what all network requests are allowed to be done, either from the users perspective or the servers.