Breaking change in home 0.5.12 patch update.

[lvboudre]

Problem

Updating from 0.5.11 to 0.5.12 cause makes the MSRV go from 1.81 to 1.88 which is breaking change for most users.

Steps

No response

Possible Solution(s)

No response

Notes

No response

Version

[epage]

The general ecosystem consensus on this is that raising an MSRV is not a breaking change (for a lot of reasons). We have some comments on this at https://doc.rust-lang.org/cargo/reference/semver.html#env-new-rust.

Note that we just had #16197 opened for this specific version bump which is closed in favor of #14944 which is closed because of the decision of the cargo team recorded in #13270.

Note that it may be a good idea to commit your lockfile which would cause your CI to not break in situations like this. We also have support an MSRV-aware resolver that can be opted-into via config without raising your MSRV, only requiring dependency updates to be done with a new enough version.

Closing as a duplicate of #14944.

[lvboudre]

@epage

I have to disagree, it is breaking change for people who build dynamic linked library where Rust ABI is not compatible across compiler version!
Breaking the ABI should not be considered a non-breaking change.

[WilfredAlmeida]

I agree with @lvboudre, this broke my build a few mins ago