You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
CI: Windows runners should not be pinned to windows-2022 #488
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.
Some additional motivation for the bump, from downstream testing in querychat's maps work — in case it helps prioritize:
Arrow registered-table fixes (1.5.5). ggsql builds with vtab-arrow and registers Arrow tables, so these are on a hot path: OR/IN predicate pushdown to registered Arrow tables, and error handling for consumed Arrow results.
Spatial fixes (1.5.4–1.5.6). Relevant now that DRAW spatial exists: Parquet GeoArrow CRS serialization and geometry stats checkpointing fixes (1.5.4), geometry row-group pruning with nulls/empty (1.5.6).
General bugfix drift. 1.5.3–1.5.6 are bugfix releases (optimizer, UNNEST/LIMIT pushdown, JSON handling, ICU strptime timezone state leaks); 1.5.3 also statically links jemalloc on Linux. The release notes call out no breaking changes for embedders. One duckdb-rs API note: 1.10506 (DuckDB 1.5.6) makes Config::set() return errors instead of panicking.
Activity
cpsievert commentedon Oct 14, 2026
Some additional motivation for the bump, from downstream testing in querychat's maps work — in case it helps prioritize:
vtab-arrowand registers Arrow tables, so these are on a hot path: OR/IN predicate pushdown to registered Arrow tables, and error handling for consumed Arrow results.DRAW spatialexists: Parquet GeoArrow CRS serialization and geometry stats checkpointing fixes (1.5.4), geometry row-group pruning with nulls/empty (1.5.6).Config::set()return errors instead of panicking.