Fix release CI

[patrickelectric]

At the moment release CI is broken, it appears that some necessary changes in cargo-workspaces is still not available to allow deployment of multiple crates in an workspace. It's necessary for us to come up with a solution meanwhile.

[pv42]

As I understand the problem is that crate-interdepence via paths is not allowed on crates.io while using versions breaks tests that depend on changes ahead of the latest release.
Is there anything preventing the use of both at the same time ?

[patrickelectric]

As I understand the problem is that crate-interdepence via paths is not allowed on crates.io while using versions breaks tests that depend on changes ahead of the latest release. Is there anything preventing the use of both at the same time ?

How do you suggest to have both simultaneously ? The release should be an automatic operation.

[pv42]

Like this (this is a dev dependency but should be the same)
https://github.com/tokio-rs/tokio/blob/1ac8dff213937088616dc84de9adc92b4b68c49a/tokio-macros/Cargo.toml#L30

tokio = { version = "1.0.0", path = "../tokio", features = ["full"] }

[joaoantoniocardoso]

If it helps to know, tokio uses workspaces resolver = "2"

[pv42]

I don't think the resolver matters since the change seems to be mostly about features.
Anyways here is a workspace on resolver 1 (since it is edition 2018) that uses it: hdf5 Accidentally linked a fork from this hdf5