TLDR

cargo msrv --output-format json --all-features verify --target thumbv7em-none-eabihf does not respect the --target argument if it is behind the verify command.

Details

In my case, I would like to combine cargo-minimal-versions with cargo-msrv. I use this command line:

cargo minimal-versions msrv --output-format json --all-features --target thumbv7em-none-eabihf verify

This internally runs:

• cargo hack msrv --output-format json --all-features --target thumbv7em-none-eabihf verify
• cargo msrv --output-format json --all-features verify --target thumbv7em-none-eabihf

Which then causes:

{"type":"meta","instance":"cargo-msrv","version":"0.16.0-beta.22","sha_short":null,"target_triple":"x86_64-pc-windows-msvc","cargo_features":"default,rust_releases_dist_source","rustc":"1.79.0"}

... dropping the thumbv7em-none-eabihf, albeit not causing an error/warning.

I don't know why cargo hack switches the order of the arguments, but it seems that cargo-msrv does not respect the --target argument if it comes after the verify command.