-
Notifications
You must be signed in to change notification settings - Fork 197
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Reunify Cargo workspace #958
Conversation
# TODO(tarcieri): re-enable when `zeroize` compatibility can be resolved | ||
#[dev-dependencies.hpke] | ||
#git = "https://github.com/rozbb/rust-hpke" | ||
#rev = "3c795445f38317d6a0868259caf3e87916548356" | ||
#default-features = false | ||
#features = [ "x25519" ] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
cc @rozbb
This no longer works due to a conflict in the zeroize
versions required by cipher
(1.5) and x25519-dalek
as pulled in by hpke
:
error: failed to select a version for `zeroize`.
... required by package `x25519-dalek v1.2.0`
... which satisfies dependency `x25519-dalek = "^1.2"` of package `hpke v0.8.0 (https://github.com/rozbb/rust-hpke?rev=3c795445f38317d6a0868259caf3e87916548356#3c795445)`
... which satisfies git dependency `hpke` of package `kem v0.1.0 (src/RustCrypto/traits/kem)`
versions that meet the requirements `=1.3` are: 1.3.0
all possible versions conflict with previously selected packages.
previously selected package `zeroize v1.5.3`
... which satisfies dependency `zeroize = "^1.5"` (locked to 1.5.3) of package `cipher v0.4.3 (/Users/bascule/src/RustCrypto/traits/cipher)`
failed to select a version for `zeroize` which could resolve this conflict
Hopefully the next releases of Dalek remove the pinning.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ugh that's annoying. Thanks for taking care of it. I'll re-enable once x25519-dalek v2.0 drops
39f2c08
to
c8cf795
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do not forget to remove Cargo.lock from the re-unified crates.
Aah yeah, good point |
Places all crates into a single Cargo workspace again. Removing the toplevel Cargo.toml when running CI on legacy pre-2021 edition crates should suffice to let them retain their current MSRV.
c8cf795
to
0517415
Compare
Now that #958 has recombined all of the crates into a single workspace, these jobs can be recombined too.
Now that #958 has recombined all of the crates into a single workspace, these jobs can be recombined too.
Now that #958 has recombined all of the crates into a single workspace, these jobs can be recombined too.
Places all crates into a single Cargo workspace again.
Removing the toplevel Cargo.toml when running CI on legacy pre-2021 edition crates should suffice to let them retain their current MSRV.