diff --git a/.github/workflows/pypi-publish.yml b/.github/workflows/pypi-publish.yml
index 5f45ba68c..4f883aec1 100644
--- a/.github/workflows/pypi-publish.yml
+++ b/.github/workflows/pypi-publish.yml
@@ -21,7 +21,7 @@ permissions:
   contents: read
 
 # Without this, a force-push to a PR leaves the previous run going -- including
-# a ~74 minute Windows job and a billed arm64 wheel build.
+# a long fat-LTO Windows job and a billed arm64 wheel build.
 concurrency:
   group: ${{ github.workflow }}-${{ github.event.pull_request.number || github.ref }}
   cancel-in-progress: true
@@ -123,8 +123,11 @@ jobs:
           path: target/wheels/lancedb-*.whl
           if-no-files-found: error
   windows:
-    timeout-minutes: 90
-    runs-on: windows-latest
+    # The fat-LTO build of the `lancedb` crate does not finish within 90 minutes
+    # on the 4-core standard runner, so use the 8-core larger runner with extra
+    # headroom.
+    timeout-minutes: 150
+    runs-on: windows-2025-8x-x64
     env:
       # link.exe is single-threaded and the long pole on Windows builds. Use
       # rustc's bundled lld-link instead.
@@ -145,7 +148,7 @@ jobs:
       # or the default branch -- so with no run on main there is nothing that
       # can populate an entry the release build would be allowed to read. Fixing
       # this needs a main/nightly trigger (which would also catch wheel-build
-      # breakage before a release); the ~74 minutes here is otherwise dominated
+      # breakage before a release); the build time here is otherwise dominated
       # by the fat-LTO link, which no cache avoids.
       - uses: ./.github/workflows/build_windows_wheel
         with: