Repository navigation
Conversation
Move the embedded engine from v2.0.0-alpha46057 (b15358c371) to the v2.0.0 release (d54cbbe3df). The wrapper now downloads DuckDB's published static-library archives from the upstream v2.0.0 release and pins their SHA-256 values. A GA release publishes permanent assets, so Fanout no longer needs its own mirror of preview build archives. No built-in was added, removed, or retyped, so the function snapshot changes only its engine header. No upstream license or notice file changed between the two commits. No code change was needed. The startup check confirms duckdb_library_version() reports v2.0.0.
Member
Author
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.
What changed
Fanout embeds the DuckDB
v2.0.0LTS release (d54cbbe3df) instead of thev2.0.0-alpha46057preview (b15358c371).The wrapper now downloads the static-library archives directly from DuckDB's upstream
v2.0.0GitHub release and pins their SHA-256 values. Preview builds needed Fanout's ownduckdb-*mirror because staging artifacts were not permanent. A GA release publishes permanent assets, so the mirror is no longer used.No built-in was added, removed, or retyped, so the function snapshot changes only its engine header. No upstream LICENSE, NOTICE, or COPYING file changed between the two commits, so only the notice header moves.
Verification
just checkjust test-raceManual: with an empty cache, the wrapper downloaded the upstream osx-arm64 archive, verified its checksum, and built. The startup check confirms
duckdb_library_version()reportsv2.0.0. Linux archives are pinned from the same upstream release and CI exercises them.