Closed iamnotacake closed 1 year ago
I don't think this fixes the issue. RustThemis CI jobs didn't run here, but I'm thinking they won't pass.
rust-version
in Cargo.toml only instructs Cargo to fail compilation earlier instead of when reaching the dependency. It does not make the new version auto-install or anything like that.
The linked job fails because one of the transitive dependencies requires Rust 1.59 now. I see three ways around it:
rayon
/rayon-core
dependency to an older version in Cargo.toml of benchmarks. Unpin when we bump MSRV.so, lets pin version of the dependency? can we do it, @iamnotacake ?
One of dev dependencies pulls rayon 1.7.0, and its dependency rayon-core 1.11.0 now requires rust 1.59+
Freeze
rayon
so it will pull a bit olderrayon-core
See failed job for the cause of this PR
Checklist