[VGSML]

DuckDB v2.0.0 was released on 2026-10-21. hugr_node builds duckdb-acl, tresor and acl-otel in, so the four move the same day.

submodule	from	to
duckdb	f8f3f4d	d54cbbe (v2.0.0)
duckdb-acl	8d0c1d9	41ec046 (spec 141, #250)
tresor	d7f2a1e	036180c (its spec 038, #67)
acl-otel	8542cad	3916552 (its spec 027, #56)
extension-ci-tools	39ffc46	fe955ed

• The node is v2.0.0 now, not a commit.
  • duckdb 2.0 no longer reads git describe. Without a given version, a build is v2.0.0-dev<commits> and names its extensions' folder after the commit.
  • The Makefile now sets DUCKDB_VERSION ?= v2.0.0, to be bumped with the pin. With it, the node's library_version, its release's extensions and the image label all read v2.0.0.
  • So a node installs from repositories that serve v2.0.0, and kista can mirror DuckDB's own repositories. They publish nothing for a dev build. Until now the release shipped f8f3f4dcd9.
• publish_to_kista.sh accepts a release version. A vX.Y.Z version goes in as kista's release kind; a commit stays dev. A CPP build is served under its exact version and needs no C API maximum. The script used to refuse a release version.
• The distribution builds the tag: duckdb_version: v2.0.0.
• Nothing in src/ changes.

Local gate (macOS, HUGR_NODE_E2E=1 HUGR_NODE_RELEASE=1), all green:

• The build is v2.0.0 at d54cbbe3df, and the extensions' footers read v2.0.0.
• test/sql/*: 982 assertions in 13 files. test-cpp: 4.
• test-e2e, all PASS:
  • tresor in the cluster;
  • acl_otel in hugr_node;
  • a node bootstraps itself: postgres_scanner is published to kista as v2.0.0, release kind;
  • the hugr type across processes;
  • the hugr type's identity through tresor.

Still to come in CI: the release's dry run (the image's e2e) and the distribution build.

🤖 Generated with Claude Code

https://claude.ai/code/session_01LdLs2iBQygBKtsApdH9Sxi