Use cargo publish --workspace instead of a custom publish script

[bjorn3]

Feature

See title

Benefit

This would allow getting rid of https://github.com/bytecodealliance/wasmtime/blob/main/scripts/publish.rs and in particular having to explicitly specify which packages to publish and in what order. It should also make publishing faster by publishing multiple crates at once and only waiting for the publish to be propagated when publishing a crate that has a just published crate as dependency.

Implementation

TODO: Do you have an implementation plan, and/or ideas for data structures or
algorithms to use?

Alternatives

TODO: What are the alternative implementation approaches or alternative ways to
solve the problem that this feature would solve? How do these alternatives
compare to this proposal?

[alexcrichton]

While I'd like to take advantage of this, there's a few reasons I haven't tried to pull the trigger yet:

• We'd need a flag like --idempotent. Inevitably publishes go wrong and being unable to restart a publish is a bit of a deal breaker.
• Over time we've packed a lot of other bits into publish.rs, such as verifying crates build from packaged sources, verifying everything has the right ownership, and automatically bumping versions.

I've no doubt that publish --workspace is faster, but it's not really the long poll in our publication process anyway, so I'm not too worried about it personally.

[bjorn3]

We'd need a flag like --idempotent. Inevitably publishes go wrong and being unable to restart a publish is a bit of a deal breaker.

👍

such as verifying crates build from packaged sources

That is basically cargo package --workspace without --no-verify, right?

[alexcrichton]

Almost yeah, we also test that it builds and at least locally cargo package --workspace doesn't look like it's building the crates, it's just packaging them. For the wasmtime repo cargo package --workspace also looks to fail since it's packaging publish = false packages which otherwise aren't compatible with packaging.