chore: bump DuckDB targets to v1.4.5 (LTS) and v1.5.4 (latest)#86
Merged
Conversation
Update both CI build matrices and the local toolchain to the new DuckDB patch releases, replacing v1.4.4 / v1.5.3. - Submodules: duckdb -> v1.5.4, extension-ci-tools -> v1.5-variegata - CI (MainDistributionPipeline.yml): the two build/deploy pairs now target duckdb v1.4.5 via the rolling ci-tools branch v1.4-andium (LTS) and duckdb v1.5.4 via v1.5-variegata (latest). Upstream publishes no per-patch ci-tools branches for v1.4.5/v1.5.4, so the rolling line branches are used (matches ../erpl). - Re-enable windows_amd64 on the LTS line to test whether the rolling v1.4-andium toolchain fixes the prior MSVC /Zc:__cplusplus->MinGW failure. - Remove duckdb_patches/0001-fmt-remove-checked-array-iterator.patch: the upstream fix (duckdb/duckdb@0c19d698ca) now ships in both v1.4.5 and v1.5.4. apply_duckdb_patches now tolerates an empty patch directory. - python/pyproject.toml: dev duckdb pin -> 1.5.4; package version -> 2026.6.17 (adopt date-based release scheme, mirroring ../erpl). - README: DuckDB badge -> 1.4.5 LTS | 1.5.4 Verified locally against v1.5.4: build clean, full SQL suite green (3296 assertions / 42 cases), Python suite green (253 passed).
Contributor
Author
|
✅ CI fully green (40 checks pass, 0 failures) across both DuckDB lines. Windows-on-LTS experiment succeeded: the |
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 both CI build matrices and the local toolchain from DuckDB v1.4.4 / v1.5.3 to the new patch releases v1.4.5 (LTS) and v1.5.4 (latest), and updates
extension-ci-tools.Changes
duckdb→v1.5.4,extension-ci-tools→v1.5-variegata(tip).MainDistributionPipeline.yml): the two build/deploy pairs now target:v1.4.5via rolling ci-tools branchv1.4-andiumv1.5.4via rolling ci-tools branchv1.5-variegata../erpl).windows_amd64re-enabled on the LTS line to test whether the rollingv1.4-andiumtoolchain resolves the prior MSVC/Zc:__cplusplus→ MinGW failure. If the LTSwindows_amd64job fails on that issue, it will be re-excluded.duckdb_patches/0001-fmt-remove-checked-array-iterator.patchis obsolete — the upstream fix (duckdb/duckdb@0c19d698ca) now ships in both v1.4.5 and v1.5.4.apply_duckdb_patchesnow tolerates an empty patch directory.duckdbpin →1.5.4; package version →2026.6.17(adopt date-based release scheme, mirroring../erpl).1.4.5 LTS | 1.5.4.Local verification (against v1.5.4)
GEN=ninja make release— clean build; extension loads,PRAGMA version→v1.5.4 (Variegata).make test_release— all SQL tests passed (3296 assertions, 42 cases; 3 OpenVINO env-skips).Notes