Tracking issue for windows-sys 0.61 update

[taiki-e]

This is a tracking issue for windows-sys 0.60 -> 0.61 update.

Note

Normally humans do not need to open PRs for updates. That is what Dependabot should do, and the PR for updates by human is welcome only if the PR opened by the bot has a CI issue.

The bot only checks for dependencies once a week, so the bot's PRs may not yet exist at the time you are interested in them, but I would still recommend leaving that task to the bot. (The exception is if you worked on the update in all the above crates, otherwise things basically go along with the slower upstream crates, so a PR that is a bit faster than the bot but do the same thing is not usually helpful in getting things done faster. Rather, it increases the number of PRs that the maintainer has to deal with...)

Crates

• bytecodealliance/rustix (external)
  • update bytecodealliance/rustix@7b32af6
  • release 1.1.1
• async-fs
  • update Update windows-sys requirement from 0.60 to 0.61 async-fs#50
  • release Release 2.2.0 async-fs#51
• polling
  • rustix release
  • update Update windows-sys requirement from 0.60 to 0.61 polling#251
  • release Release 3.11.0 polling#252
• async-io
  • polling release
  • update Update windows-sys requirement from 0.60 to 0.61 async-io#243
  • release Release 2.6.0 async-io#244
• async-signal
  • async-io release
  • update Update windows-sys requirement from 0.60 to 0.61 async-signal#55
  • release Release 0.2.13 async-signal#56
• async-process
  • async-signal release
  • update Update windows-sys requirement from 0.60 to 0.61 async-process#104
  • msrv bump is missing Bump MSRV to 1.71 async-process#106
  • release Release 2.5.0 async-process#107

https://github.com/search?q=org%3Asmol-rs+%2Fwindows-sys%2F+language%3ATOML&type=code&l=TOML

---

Related:

• Tracking issue for windows-sys 0.60 update #347