-
Notifications
You must be signed in to change notification settings - Fork 2.7k
Open
Labels
C-feature-requestCategory: proposal for a feature. Before PR, ping rust-lang/cargo if this is not `Feature accepted`Category: proposal for a feature. Before PR, ping rust-lang/cargo if this is not `Feature accepted`Command-publishS-needs-infoStatus: Needs more info, such as a reproduction or more background for a feature request.Status: Needs more info, such as a reproduction or more background for a feature request.
Description
Problem
Sometimes a cargo publish run of multiple packages will fail. It is then necessary to restart it.
It would be nice if we could run the whole publication from the top, and simply skip crates that were already published. There are probably other uses.
Proposed Solution
cargo publish --idempotent
If the current version of the crate has already been published, skips the crate and exits with a success status.
(Ideally it would download the crate and check it's identical to what is proposed to publish now, but I think that crates.io does unpredictable-to-cargo mangling of the uploaded data which makes such a check infeasible.)
Notes
No response
MOZGIII, skos-ninja, raviqqe and ntrinquier
Metadata
Metadata
Assignees
Labels
C-feature-requestCategory: proposal for a feature. Before PR, ping rust-lang/cargo if this is not `Feature accepted`Category: proposal for a feature. Before PR, ping rust-lang/cargo if this is not `Feature accepted`Command-publishS-needs-infoStatus: Needs more info, such as a reproduction or more background for a feature request.Status: Needs more info, such as a reproduction or more background for a feature request.