feat: replace ctrlc with manual syscalls

The `ctrlc` library uses a semaphore in its handler on windows, which we
do not need since we're not doing anything with the handler except
suppressing the default behavior. This replaces the library with the
direcy syscalls to set a console control handler that does nothing,
without a semaphore.

Author: demosdemon

.github/workflows/ci.yml

@@ -43,6 +43,11 @@ jobs:
           - macos-latest
           - windows-latest
         rust:
+          - '1.86'
+          - '1.87'
+          - '1.88'
+          - '1.89'
+          - '1.90'
           - stable
           - beta
           - nightly

Cargo.lock

@@ -32,5 +32,6 @@ tracing = "0.1.41"
 tracing-subscriber = { version = "0.3.20", features = ["env-filter"] }
 uriparse = "0.6.4"
 
-[target."cfg(windows)".dependencies]
-ctrlc = "3.5.0"
+[target."cfg(windows)".dependencies.windows-sys]
+version = "0.61.2"
+features = ["Win32_Foundation", "Win32_System_Console"]

crates/git-remote-codecommit/Cargo.toml

@@ -145,17 +145,32 @@ fn exec_replace(mut cmd: std::process::Command) -> anyhow::Result<ExitCode> {
 
 #[cfg(windows)]
 fn exec_replace(mut cmd: std::process::Command) -> anyhow::Result<ExitCode> {
+    #![expect(unsafe_code)]
+    use windows_sys::Win32::Foundation::FALSE;
+    use windows_sys::Win32::Foundation::TRUE;
+    use windows_sys::Win32::System::Console::SetConsoleCtrlHandler;
+    use windows_sys::core::BOOL;
+
     use crate::nightly::ExitCodeExt;
 
+    unsafe extern "system" fn ctrlc_handler(_: u32) -> BOOL {
+        // Do nothing; let the child process handle it.
+        TRUE
+    }
+
     // windows and other non-unix platforms don't support `execvp`, so we can't
     // replace the current process. Instead, we need to spawn a new process and
     // set up the pipes.
 
-    // We setup a ctrlc handler and ignore it because on windows, this signal is
-    // sent to all processes attached to the console, including the parent
-    // process. Therefore, by ignoring the ctrl-c, we let the child handle the
-    // signal and exit. We can reap the process normally.
-    ctrlc::set_handler(|| {}).context("failed to set ctrl-c handler")?;
+    // SAFETY: We setup a ctrlc handler and ignore it because on windows, this
+    // signal is sent to all processes attached to the console, including the
+    // parent process. Therefore, by ignoring the ctrl-c, we let the child
+    // handle the signal and exit. We can reap the process normally.
+    unsafe {
+        if SetConsoleCtrlHandler(Some(ctrlc_handler), TRUE) == FALSE {
+            anyhow::bail!("failed to set ctrl-c handler");
+        }
+    }
 
     let exit = cmd
         .spawn()