chore: update windows-sys dependency to 0.61

[vthib]

Anstyle crates are the only dependencies that are still pulling the windows-sys 0.61 on my projects.

There is an existing PR for it by the renovate bot:
#272 , but I figured i'd provide a PR that should be pass the CI to be easily mergeable.

This update requires a bump of MSRV to 1.71

[epage]

This update requires a bump of MSRV to 1.71

We're not doing an MSRV bump at this time which is why #272 is still open

[vthib]

Can you elaborate on why a bump from 1.66 (released in december 2022) to 1.71 (released in july 2023) is not acceptable? What is the MSRV goal of this project, that is how long ago should a version have been released to be acceptable as a MSRV?

[epage]

I don't really have a solid policy atm. anstyle is meant to be a low level, fundamental piece of software for easy integration with other libraries. While anstream is higher level`, it is meant to be fairly applicable. This exists in a shared workspace where I tried to keep the MSRV the same.

Looking at our top direct dependents

• toml's MSRV is 1.76
• env_logger's MSRV is 1.71
• clap's is 1.74
• winnow's is 1.65

We already excluded Winnow with the 1.66 bump.

Other important deps include:

• annotate-snippets at 1.66
• libtest-mimic at 1.65
• snapbox at 1.66
• ansi_colours which is unset but 2018 edition
• terminal-colorsaurus at 1.74
• libtest2 at 1.76 but I am considering dropping this to be as low as possible (schemars is the biggest limitation atm but I might just carve out an exception for it)

[hanna-kruppe]

I think it would be really unfortunate if using windows-sys 0.61 was blocked on an MSRV bump. I opened #282 to describe why this matters and to propose allowing both 0.60 and 0.61 as long as anstream has MSRV < 1.71.