Skip to content

chore: bump DuckDB to v1.5.6 - #85

Merged
smithclay merged 1 commit into
mainfrom
chore/duckdb-v1.5.6
Oct 1, 2026
Merged

smithclay merged 1 commit into
mainfrom
chore/duckdb-v1.5.6

Conversation

@smithclay

Copy link
Copy Markdown
Owner

Bumps DuckDB from v1.5.5 to v1.5.6.

  • duckdb submodule → v1.5.6; extension-ci-tools → v1.5.6
  • CI workflows (MainDistributionPipeline.yml, pages.yml): reusable workflow refs, duckdb_version/ci_tools_version, DAEMON_DUCKDB_VERSION, pinned CLI download, pytest duckdb== pin
  • docker/duckdb-otlp-server/Dockerfile DUCKDB_VERSION ARG (kept in sync with DAEMON_DUCKDB_VERSION)
  • Makefile VERSION_FIELD stamp
  • README, AGENTS.md, site docs, Colab notebook, test/server + test/manual duckdb== pins

Not changed on purpose:

  • The wasm demo stays on v1.5.4 to match duckdb-wasm@1.33.1-dev56.0 (only its comments were updated).
  • The Windows/fmt workflow comments still say v1.5.5, because that's the release where the fix landed.

Not built locally; CI is the verification.

🤖 Generated with Claude Code

Bump native submodule pin, extension-ci-tools, CI workflows, Dockerfile,
Makefile version stamp, docs, server/manual test harnesses, and notebook
from v1.5.5 to v1.5.6. The wasm-demo build stays pinned to v1.5.4 to match
duckdb-wasm@1.33.1-dev56.0; comments updated to reflect the divergence.
The Windows/fmt workflow comments keep naming v1.5.5, since that is the
release where the fix landed.

Co-authored-by: Claude <noreply@anthropic.com>
@smithclay
smithclay merged commit f8f3966 into main Oct 1, 2026
32 checks passed
@smithclay
smithclay deleted the chore/duckdb-v1.5.6 branch October 1, 2026 17:24
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.

1 participant