Breaking dependencies

[quasi-coherent]

Describe The Bug

This commit effectively changed the MSRV of cargo-make from 1.81 to 1.88.

To Reproduce

> $ git clone git@github.com:sagiegurari/cargo-make.git && cd cargo-make
> $ git checkout f573e75^
> $ cargo +1.86.0 c
...
...
    Checking attohttpc v0.28.5
    Checking duckscriptsdk v0.11.1
    Checking cargo-make v0.37.24 (/me/tmp/cargo-make)
    Finished `dev` profile [unoptimized + debuginfo] target(s) in 58.14s

> $ git checkout master
> $ cargo + 1.86.0 c
error: rustc 1.86.0 is not supported by the following package:
  home@0.5.12 requires rustc 1.88
Either upgrade rustc or select compatible dependency versions with
`cargo update <name>@<current-ver> --precise <compatible-ver>`
where `<compatible-ver>` is the latest version supporting rustc 1.86.0

[quasi-coherent]

I know this is more of a home problem. They suggest to not use home anymore, but I opened the issue here because ideally it's a patch version bump of cargo-make where the change is:

Author: John Doe <jd@gmail.com>
Date:   Tue Nov 4 16:51:31 2025 -0500

    release 0.37.25: bump home@0.5.12

diff --git a/Cargo.toml b/Cargo.toml
index e33cac27..b857d790 100644
--- a/Cargo.toml
+++ b/Cargo.toml
@@ -58,7 +58,7 @@ fsio = { version = "^0.4", features = ["temp-path"] }
 git_info = "^0.1.3"
 glob = "^0.3.2"
 hex = "0.4.3"
-home = "0.5.11"
+home = "0.5.12"
 ignore = "^0.4"
 indexmap = { version = "^2", features = ["serde"] }
 itertools = "^0.14"

Then cargo-make-0.37.25 will always have home@0.5.12. And cargo-make-0.37.24 would have home@0.5.11, and something like cargo install --version=0.37.24 cargo-make will not work one day and not the next.

Since the lockfile when 0.37.24 was released had home@0.5.11, the workaround is to add a --locked to that command:

> $ cargo install --version=0.37.24 --locked cargo-make