Skip to content

CI: run release tests on the DuckDB version the extension is built for - #2

Merged
asubbarao merged 1 commit into
fix/claude-conversation-evidencefrom
luna/ci-windows
Oct 1, 2026
Merged

asubbarao merged 1 commit into
fix/claude-conversation-evidencefrom
luna/ci-windows

Conversation

@asubbarao

Copy link
Copy Markdown
Owner

Every Build extension binaries job failed at the first test with "built specifically for DuckDB version v1.5.5 … this version is v1.5.6": the sqllogictest runner installed the latest DuckDB while the extension is stamped for TARGET_DUCKDB_VERSION. The Makefile now pins the test runtime to TARGET_DUCKDB_VERSION, with five regression tests in scripts/test_duckdb_runtime_version.py.

Green: run 36784057353 (7 passed, 1 skipped; Linux, macOS arm64/x86_64, Windows static and MinGW).

The alternative (branch luna/ci-macos, fb2cf56) moves the whole extension to DuckDB 1.5.6, which is also green, but the local CLI, dev server and replica all run 1.5.5 and would reject a 1.5.6 build. Upgrading is a separate, stack-wide decision.

🤖 Generated with Claude Code

@asubbarao
asubbarao merged commit ddcc538 into fix/claude-conversation-evidence Oct 1, 2026
16 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants