Bump windows crate 0.61 -> 0.62 (fixes the Windows release build)

The third Windows release failure was a genuine cross-version type mismatch: process-wrap 9.1.0 wraps windows 0.62's PROCESS_CREATION_FLAGS in its CreationFlags wrapper, while the workspace pinned windows 0.61 — the CREATE_NEW_PROCESS_GROUP | CREATE_NO_WINDOW constants we pass came from a different nominal type. Aligning the workspace on 0.62 leaves a single windows crate in the graph. Windows code cannot be compiled on this host (a full cross-typecheck dies in ring's C build), so the change is verified by auditing every windows-crate item our cfg(windows) code imports (25 items across 9 files) plus all seven Win32_* feature names against the actual windows-0.62.2 registry sources — all present — and by confirming process-wrap's CreationFlags field is the same 0.62 type our call site now names.
2026-07-18 05:52:48 -04:00
parent 641c73899c
commit 48e7f0e338
2 changed files with 33 additions and 122 deletions
@@ -250,7 +250,7 @@ walkdir = "2"
 webbrowser = { version = "1.0.4" }
 which = "8"
 keyring = { version = "3", default-features = false }
-windows = { version = "0.61", features = ["Win32_Security", "Win32_Security_Authorization", "Win32_Foundation", "Win32_System_Threading", "Win32_System_JobObjects", "Win32_System_Console", "Win32_System_Pipes"] }
+windows = { version = "0.62", features = ["Win32_Security", "Win32_Security_Authorization", "Win32_Foundation", "Win32_System_Threading", "Win32_System_JobObjects", "Win32_System_Console", "Win32_System_Pipes"] }
 wiremock = "0.6"
 wl-clipboard-rs = "0.9"
 kigi-acp-lib = { path = "crates/codegen/kigi-acp-lib" }