I assume you updated rust-rustversion to update rust-anyhow? If so, I have looked at the Cargo.toml of anyhow. It is very picky in the version of dependents, so if in the future we update rust-rustversion again, rust-anyhow will fail to build. To be robust to that, the Cargo.toml needs to be patched to be less picky, or alternatively you could wait for antioxidant which ignores the version specifications entirely.
Nevermind, from <https://doc.rust-lang.org/cargo/reference/specifying-dependencies.html>:
"0.1.12"is a version requirement. Although it looks like a specific version of the
timecrate, it actually specifies a range of versions and allows SemVer compatible updates. An update is allowed if the new version number does not modify the left-most non-zero digit in the major, minor, patch grouping. In this case, if we ran
cargo update -p time, cargo should update us to version
0.1.13if it is the latest
0.1.zrelease, but would not update us to
0.2.0. If instead we had specified the version string as
1.0, cargo should update to
1.1if it is the latest
1.yrelease, but not
2.0. The version
0.0.xis not considered compatible with any other version.
(if it used = or <=, that would be a different manner)