cargo publish multiple packages at once

[alexcrichton]

It would be nice to have a flag to cargo publish which publishes all local packages in a DAG fashion.

Non-atomic publish was added in #14433, stabilization is being tracked in #10948

Testing instructions: #1169 (comment)

Notes (edit ehuss):

• publish multiple crates, races with dependencies #9507 would block this
• It would be nice if it supported atomic publishing.
• --dry-run should work correctly (will need to pretend that the previous crates have been published, maybe via patch?) See also Add a dry-run publish API crates.io#1515.
• See New publish API crates-io-cargo-teams#82 for other considerations for a new publish API to better accommodate this.

Blocking issues

• Wrong workspace publication order in the presence of dev-dependencies #15412

Non-blocking issues

• cargo package (and hence cargo publish) verify step is slow from doing a full build #14941

[wycats]

This would be awesome ;)

[huonw]

I suspect we may want to have a story with #883 if/when we implement this: I could easily imagine unintentionally publishing crates by not realising that I'm depending on them.

[botev]

Is there any progress on this? I think this would a very good thing to have. One of the nice things about crates is that they are modular, thus reduce the compile time of larger projects. However, if you are developing a large library compile times can get pretty slow (when it hits >2min I start to compile after 50% of the fixing, so it can compile while I'm fixing the other 50% of the issues). In this case you can split the library into sub-crates, where each sub-crate is in some sense standalone, or a build-up over "core" structure. However, each one of them would not make any sense on its own. Publishing each individually does not make any sense also and not packaging it together. If we can have this kind of publish --all this would give as an option to reduce compile times without any drawback from the user and publishing side of the library.

[matthiasbeyer]

Any updates whether this will be implemented and when?

[wycats]

@matthiasbeyer I think this fell through the cracks when we did workspaces. This issue was supposed to track wrapping --all up for publish but I guess it got lost since it was originally opened earlier?

@alexcrichton what's the status?

[alexcrichton]

@wycats AFAIK this has always been in the 'nice to have' category and hasn't progressed to the 'someone has put time into designing this' category.

[matthiasbeyer]

One thing I just thought about: When doing a workspace release, cargo should build everything and after everything is fine, publish all crates at once... if that is even possible. Not like "build & publish the first crate and continue for each crate" but rather "build everything, then publish everything".