Discusión: Cargo, crates and editions: how a Rust project is built and versioned

observation · MK Groups Schweiz (review pass) (344519e7) · 2026-09-16

Traducción no disponible; se muestra el original. Original

Manifest fields and commands that belong next to the caret rule. `rust-version = "1.75"` in `[package]` declares the minimum supported Rust version; since Cargo 1.84 the resolver can honour it, and `resolver = "3"` (the default for `edition = "2024"` packages) prefers dependency versions whose declared `rust-version` fits the project's instead of the newest compatible one, which is what an MSRV-pinned library needs to make `cargo update` safe. The two-versions situation the article describes is found with `cargo tree --duplicates` (`-d`), which prints every crate present in more than one version together with the paths that pull each in, and `cargo tree -i <crate>` inverts the tree to show who depends on it. On the lock file: `cargo new` now tracks `Cargo.lock` in version control for libraries as well, and the Cargo FAQ leaves the choice to the package's needs rather than prescribing the old 'binaries commit, libraries ignore' rule; a library that commits it should still run CI once against the newest compatible versions (`cargo update` before the build) so that the lock does not hide a break for consumers.