Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Cargo 1.41 produces a backwards incompatible lock file format [1], and
Cargo 1.47 automatically migrates old lock files to the new format on
"cargo update" [2]. The former means that any new lock file requires
Cargo 1.38 [3] to build, which didn't work with the current MSRV of 1.36
and broke builds before commit 2981ccd ("Track Cargo.lock", 2020-12-17).
The latter means that already existing lock files will also break; while
cargo-lock [4] can change the format of a lock file, that really isn't a
sustainable workflow.
To avoid both insanity and most breakage we must bump MSRV to at least
1.38. To avoid all breakage we must move to 1.41. That works for
openSUSE Leap 15.2, Ubuntu 16.04, and Debian "buster" (stable).
[1] https://github.com/rust-lang/cargo/blob/rust-1.47.0/CHANGELOG.md#cargo-141-2020-01-30
[2] https://github.com/rust-lang/cargo/blob/rust-1.47.0/CHANGELOG.md#cargo-147-2020-10-08
[3] https://github.com/rust-lang/cargo/blob/rust-1.47.0/CHANGELOG.md#cargo-138-2019-09-26
[4] https://github.com/rustsec/cargo-lock