Problem
Cargo.toml at the workspace root declares:
[workspace.package]
rust-version = "1.80"
However, multiple transitive dependencies in the current resolved graph declare higher minimum Rust versions:
| Crate |
Declared rust-version |
home >= 0.5.12 |
1.88 |
cookie_store >= 0.22.1 |
1.88 |
time crate family |
1.85+ (edition2024 Cargo feature) |
cranelift-control >= 0.123 |
1.85+ |
Running cargo-msrv verify at Rust 1.80 fails because dependency resolution itself fails — these crates are incompatible at that toolchain.
Impact
The declared rust-version is misleading: anyone attempting to build at 1.80 (following the workspace's stated MSRV) will get a resolution error rather than a compile error with a clear MSRV message. CI that enforces MSRV (e.g., cargo-msrv verify) will report the declaration as incorrect.
Fix
Update Cargo.toml:
[workspace.package]
rust-version = "1.88"
The fork (metavacua/larql-to-sparql) already carries this change.
Optionally, also opt crates into the MSRV gate by adding rust-version.workspace = true to each crate's [package] block so that cargo-msrv verify can verify per-crate.
Problem
Cargo.tomlat the workspace root declares:However, multiple transitive dependencies in the current resolved graph declare higher minimum Rust versions:
home>= 0.5.12cookie_store>= 0.22.1timecrate familycranelift-control>= 0.123Running
cargo-msrv verifyat Rust 1.80 fails because dependency resolution itself fails — these crates are incompatible at that toolchain.Impact
The declared
rust-versionis misleading: anyone attempting to build at 1.80 (following the workspace's stated MSRV) will get a resolution error rather than a compile error with a clear MSRV message. CI that enforces MSRV (e.g.,cargo-msrv verify) will report the declaration as incorrect.Fix
Update
Cargo.toml:The fork (
metavacua/larql-to-sparql) already carries this change.Optionally, also opt crates into the MSRV gate by adding
rust-version.workspace = trueto each crate's[package]block so thatcargo-msrv verifycan verify per-crate.