cargo-minimal-versions

Cargo subcommand for proper use of -Z minimal-versions and -Z direct-minimal-versions.

• Usage
  • --direct (-Z direct-minimal-versions)
• Details
• Installation
• Related Projects
• License

Usage

$ cargo minimal-versions --help
cargo-minimal-versions

Cargo subcommand for proper use of -Z minimal-versions and -Z direct-minimal-versions.

USAGE:
    cargo minimal-versions <CARGO_SUBCOMMAND> [OPTIONS] [CARGO_OPTIONS]

CARGO_SUBCOMMANDS:
    build
    check
    test
    ...

To check all crates with minimal version dependencies:

cargo minimal-versions check --workspace

[!NOTE] (If cargo-minimal-versions determined that it is necessary to do so for a correct minimal versions check) cargo-minimal-versions modifies Cargo.toml and Cargo.lock while running and restores it when finished. Any changes you made to those files during running will not be preserved.

Normally, crates with publish = false do not need minimal versions check. You can skip these crates by using --ignore-private flag.

cargo minimal-versions check --workspace --ignore-private

If path dependencies exist, the above ways may miss the problem when you publish the crate (e.g., tokio-rs/tokio#4376, tokio-rs/tokio#4490)
By using --detach-path-deps flag, you can run minimal versions check with path fields removed from dependencies.

cargo minimal-versions check --workspace --ignore-private --detach-path-deps

--detach-path-deps (--detach-path-deps=all) flag removes all[^1] path fields by default. By using --detach-path-deps=skip-exact flag, you can skip the removal of path fields in dependencies with exact version requirements ("=<version>"). For example, this is useful for a pair of a proc-macro and a library that export it.

[^1]: To exactly, when neither version, git, nor path field is specified, an error will occur, so we will remove the path field of all of dependencies for which have version or git field.

--direct (-Z direct-minimal-versions)

If there are dependencies that are incompatible with -Z minimum-versions, it is also reasonable to use -Z direct-minimal-versions, since it is hard to maintain -Z minimum-versions compatibility in such situations.

By using --direct flag, cargo-minimal-versions uses -Z direct-minimal-versions instead of -Z minimal-versions.

cargo minimal-versions check --direct

[!NOTE] Using -Z direct-minimal-versions may miss some of the problems that can be found when using -Z minimal-versions. However, if there is a problem only in a particular version of a dependency, a problem that was missed when using -Z minimal-versions may be found by using -Z direct-minimal-versions (because the resolved dependency version is different).

Details

Using -Z minimal-versions in the usual way will not work properly in many cases. To use cargo check with -Z minimal-versions properly, you need to run at least three processes.

If I remember correctly, cargo check -Z minimal-versions doesn't really do anything. It needs to be separated into cargo update -Z minimal-versions and cargo check.

Also, dev-dependencies may raise version requirements. Ideally, remove them before run cargo update -Z minimal-versions. (Also, note that Cargo.lock is actually shared within the workspace. However as far as I know, there is no workaround for this yet.)

In addition, due to cargo's feature integration, it is not correct to run cargo check or cargo build with -p (--package) or --workspace (--all) or on virtual manifest. To handle this problem correctly, you need the workspace handling provided by subcommands such as cargo hack.

cargo-minimal-versions addresses most of these issues and makes it easy to run cargo commands with -Z minimal-versions.

See #1 and #6 for the remaining problems.

Installation

Prerequisites

cargo-minimal-versions requires nightly toolchain (to run cargo update -Z minimal-versions or cargo update -Z direct-minimal-versions) and cargo-hack (to run cargo check & cargo build proper):

rustup toolchain add nightly
cargo +stable install cargo-hack --locked

From source

cargo +stable install cargo-minimal-versions --locked

Currently, installing cargo-minimal-versions requires rustc 1.70+.

cargo-minimal-versions is usually runnable with Cargo versions older than the Rust version required for installation (e.g., cargo +1.59 minimal-versions check).

From prebuilt binaries

You can download prebuilt binaries from the Release page. Prebuilt binaries are available for macOS, Linux (gnu and musl), Windows (static executable), FreeBSD, and illumos.

# Get host target
host=$(rustc -vV | grep '^host:' | cut -d' ' -f2)
# Download binary and install to $HOME/.cargo/bin
curl --proto '=https' --tlsv1.2 -fsSL "https://github.com/taiki-e/cargo-minimal-versions/releases/latest/download/cargo-minimal-versions-$host.tar.gz" \
  | tar xzf - -C "$HOME/.cargo/bin"

On GitHub Actions

You can use taiki-e/install-action to install prebuilt binaries on Linux, macOS, and Windows. This makes the installation faster and may avoid the impact of problems caused by upstream changes.

- uses: taiki-e/install-action@cargo-hack
- uses: taiki-e/install-action@cargo-minimal-versions

Via Homebrew

You can install cargo-minimal-versions from the Homebrew tap maintained by us (x86_64/AArch64 macOS, x86_64/AArch64 Linux):

brew install taiki-e/tap/cargo-minimal-versions

Via Scoop (Windows)

You can install cargo-minimal-versions from the Scoop bucket maintained by us:

scoop bucket add taiki-e https://github.com/taiki-e/scoop-bucket
scoop install cargo-minimal-versions

Via cargo-binstall

You can install cargo-minimal-versions using cargo-binstall:

cargo binstall cargo-minimal-versions

Related Projects

• cargo-hack: Cargo subcommand to provide various options useful for testing and continuous integration.
• cargo-llvm-cov: Cargo subcommand to easily use LLVM source-based code coverage.
• cargo-config2: Library to load and resolve Cargo configuration.

License

Licensed under either of Apache License, Version 2.0 or MIT license at your option.

Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.