chore: bump bundled DuckDB to v1.5.3 - #73
Merged
Merged
Conversation
Updates the DuckDB submodule from v1.5.2 to the latest stable bugfix release v1.5.3 (released 2026-05-20), and the matching version references. - duckdb submodule: v1.5.2 -> v1.5.3 - CMakeLists.txt: DUCKDB_EXPLICIT_VERSION 1.5.2 -> 1.5.3 (+ comments) - docs: AGENTS.md (CLAUDE.md symlink), Readme.md, CONFIG_REFERENCE.md Unit tests pass (642/642) and runtime SELECT version() reports v1.5.3.
The `windows-latest` runner image was migrated and no longer exposes Visual Studio 2022, so `cmake -G "Visual Studio 17 2022"` fails at configure time with "could not find any instance of Visual Studio" (before DuckDB is even added). Pin the build job to windows-2022, which ships VS 2022, restoring the last-known-good environment. The smoke-test-windows / pack-smoke-windows jobs only run the prebuilt binary (no VS needed) and stay on windows-latest.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Updates the bundled DuckDB from v1.5.2 → v1.5.3 — the latest stable bugfix release (published 2026-05-20). Same minor line (1.5.x), bugfix-only delta.
duckdbsubmodule:v1.5.2→v1.5.3CMakeLists.txt:DUCKDB_EXPLICIT_VERSION 1.5.2 → 1.5.3(+ matching/MTcomments)AGENTS.md(and itsCLAUDE.mdsymlink),Readme.md,docs/CONFIG_REFERENCE.mdTest plan
All run locally against a from-scratch release build on Linux x86_64:
make test) — 642/642 pass, 0 failed (1 AWS test skipped as usual).SELECT version()returnsv1.5.3; server boots cleanly (no extension-cache issue).make integration-test) — 507 passed, 25 skipped. One test (test_concurrent_schema_refreshes) errored under parallel-n autowithbind: Address already in use(port-collision flake) and passes in isolation — not a 1.5.3 regression.smoke-test-linux-amd64) — server healthy,/api/v1/_config/health→status: healthy.pack-smoke-*) —pack/info/unpackround-trip OK and reproducible (identical sha256 with fixedSOURCE_DATE_EPOCH).CI will additionally run the full cross-platform build + smoke matrix (Linux amd64/arm64, macOS, Windows).