Options for running commands on a specified range of versions of cargo

[taiki-e]

This may be useful for catching issues like BurntSushi/termcolor#35, rust-lang/regex#685, rayon-rs/rayon#761 (comment), rust-lang/rust-clippy#6324.

Examples

something like:

$ cargo hack check --version-range 1.36..stable
info: running `cargo +1.36.0 check`
...
info: running `cargo +1.37.0 check`
...
...
info: running `cargo +1.47.0 check`
...
info: running `cargo +1.48.0 check` (current stable)
...

with specified step:

$ cargo hack check --version-range 1.36..stable --version-step 2
info: running `cargo +1.36.0 check`
...
info: running `cargo +1.38.0 check`
...
...
info: running `cargo +1.46.0 check`
...
info: running `cargo +1.48.0 check` (current stable)
...

[jhpratt]

Would this take point releases into account? It's probably not strictly necessary.

[taiki-e]

I would like to use rustup's major.minor channels. (i.e., point releases do not take into account, and always select the latest patch version of each minor version)

[jhpratt]

Ah, advantages of the new rustup release!

[taiki-e]

Published in 0.5.0 (#102)