Open chipshort opened 1 week ago
We ignore dev-dependencies to break cycles https://github.com/crate-ci/cargo-release/blob/06a4e446ce18217536a16f0fddb3d843db0cc36d/src/ops/cargo.rs#L434-L451
However, we should only do that if the package is missing a version
We set up cargo-release for the https://github.com/CosmWasm/cosmwasm workspace, but it seems the order of publishing for crates is not detected correctly. It tries to publish the dependent before the dependency, resulting in a failure mid-publishing.
To reproduce: From the
release/2.2
branch in cosmwasm, runcargo release 2.2.0-rc.3 -x
. It tries to publishcosmwasm-std
beforecosmwasm-schema
even though the former has a dev-dependency on the latter. This causes cargo to fail publishing. Here are the relevant outputs for when I encountered this with rc.2:Maybe the problem is that dev-dependencies are not factored into the ordering?