Skip to content

chore(deps): upgrade Go modules and the DuckDB bindings to v2.20000.0 - #501

Open
vishr wants to merge 4 commits into
mainfrom
chore/upgrade-go-deps
Open

vishr wants to merge 4 commits into
mainfrom
chore/upgrade-go-deps

Conversation

@vishr

@vishr vishr commented Nov 16, 2026

Copy link
Copy Markdown
Member

Summary

Upgrades every Go dependency to its latest release with go get -u ./..., including the DuckDB driver github.com/duckdb/duckdb-go/v2 (v2.10506.0 → v2.20000.0) and its bindings (v0.10506.0 → v0.20000.0), whose native modules moved to go.duckdb.org/libduckdb/*. This is the deferred remainder of the dependency sweep (closed #492/#418 bundled the same DuckDB driver bump without the native-integration change this PR makes).

The native engine is unchanged

Both the old and new bindings target DuckDB v2.0.0 (source d54cbbe3df, per the bindings' duckdb-release.json), which is exactly what scripts/with-duckdb.sh already pins. So:

  • SELECT version() still returns v2.0.0 (the pinned-engine and checkpoint tests assert this).
  • The reviewed built-in-function snapshot is unchanged (TestBuiltinFunctionsMatchTheReviewedSnapshot passes without regeneration).
  • The static-library checksums in scripts/with-duckdb.sh are untouched.

This is a Go binding-layer upgrade, not an engine upgrade, so it needs no new built-in review and no re-benchmark.

Static-extension loader

Bindings v0.20000.0 changed how static extensions load: their init now calls a loader symbol duckdb_register_static_extensions before any database opens. The prebuilt go.duckdb.org/libduckdb/<platform> modules define it, but Pitot deliberately links its own minimal static engine (core functions, JSON, Parquet, ICU) through scripts/with-duckdb.sh instead of those modules, so the symbol was undefined and the link failed:

Undefined symbols for architecture arm64:
  "_duckdb_register_static_extensions", referenced from: ...

internal/duckdb/native.go already registered those four extensions from its own init. It now exports duckdb_register_static_extensions with exactly those four extensions — the symbol the bindings call — and drops the duplicate self-registration from init (keeping the v2.0.0 version guard). Registration still happens once, now driven by the bindings' init.

Other upgrades

cel-go, echo, goose, grpc, modernc.org/sqlite, go-mail, prometheus/procfs, the golang.org/x/* modules, and the usual indirect set, all to latest.

Verification

  • just vet: clean.
  • just test ./internal/engine/... version/snapshot/blocklist tests (TestCheckpointScanLock*, TestBuiltinFunctionsMatchTheReviewedSnapshot, TestScalarMacrosThatRunQueriesAreBlocked): pass — SELECT version() == v2.0.0, snapshot unchanged.
  • just test ./internal/telemetry/store/... and ./internal/engine/...: pass.
  • gofmt, just go-deadcode, just test-names-check: clean.

Upgrade every Go dependency to its latest release, including the DuckDB
driver github.com/duckdb/duckdb-go/v2 from v2.10506.0 to v2.20000.0 and the
bindings from v0.10506.0 to v0.20000.0, whose native modules moved to
go.duckdb.org/libduckdb/*. The pinned native engine is unchanged: both the old
and new bindings target DuckDB v2.0.0 (source d54cbbe3df), so SELECT version()
and the reviewed built-in-function snapshot are identical and the engine's
checksums in scripts/with-duckdb.sh stay as they are.

The new bindings register static extensions through a loader symbol,
duckdb_register_static_extensions, that their init calls before any database
opens. The prebuilt platform modules define it; Pitot links its own minimal
static engine (core functions, JSON, Parquet, ICU) through scripts/with-duckdb.sh
instead, so internal/duckdb now exports that loader with exactly those four
extensions and no longer registers them a second time from its own init.
The Go dependency graph changed with the module upgrade, so the committed
THIRD_PARTY_NOTICES no longer matches it and notices-check fails. Regenerate
it (284 components).
@vishr vishr closed this Nov 16, 2026
@vishr vishr reopened this Nov 16, 2026
@vishr
vishr enabled auto-merge November 16, 2026 17:23
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