CI: Windows runners should not be pinned to `windows-2022`
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 554
- Forks
- 30
- Avg merge
- 17h 27m
- Merged PRs (30d)
- 8
Description
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.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with release-packages.yml and release-jupyter.yml, then inspect the duckdb crate dependency and its vendored fmt compatibility with MSVC 14.51. Identify a compatible duckdb release, restore both jobs to windows-latest, and verify the Windows CI jobs pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, rust
- Domain
- build-system, ci-cd
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100