The Windows CI jobs (release-packages.yml and release-jupyter.yml) are pinned to runs-on: windows-2022 as a stopgap for v0.4.1.
As of the ~2026-06-11 GitHub runner image refresh, windows-latest/windows-2025 ship Visual Studio 2026 (MSVC 14.51), and the bundled/vendored libduckdb-sys 1.10502.0 C++ compile fails.
Pinning to windows-2022 (VS2022 / MSVC 14.4x) restored the build for now. We should bump the duckdb crate to a release whose vendored fmt compiles under MSVC 14.51, then revert both jobs back to windows-latest.
The Windows CI jobs (
release-packages.ymlandrelease-jupyter.yml) are pinned toruns-on: windows-2022as a stopgap for v0.4.1.As of the ~2026-06-11 GitHub runner image refresh,
windows-latest/windows-2025ship Visual Studio 2026 (MSVC 14.51), and the bundled/vendored libduckdb-sys 1.10502.0 C++ compile fails.Pinning to
windows-2022(VS2022 / MSVC 14.4x) restored the build for now. We should bump the duckdb crate to a release whose vendored fmt compiles under MSVC 14.51, then revert both jobs back towindows-latest.