You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* feat: bundle PostHog ducklake fork (v1.0-posthog.1)
Switches the ducklake extension shipped in the duckgres and
duckgres-worker images from the upstream extensions.duckdb.org build to
PostHog's fork at https://github.com/PostHog/ducklake/releases. Mirrors
the existing httpfs override pattern.
Also adds ducklake.duckdb_extension to shouldRefreshBundledExtension so
the cached copy on a long-lived data-dir PVC is replaced when the image
ships a newer fork build — same rationale as postgres_scanner.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
* test: drop redundant ducklake refresh test
Already covered by TestSeedBundledExtensionsReplacesExistingFilesWithUpdatedContents
exercising the same code path via postgres_scanner.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
* test(k8s): assert worker loads PostHog ducklake fork
After bundling the v1.0-posthog.1 fork in Dockerfile.worker, add a kind-
cluster integration test that queries duckdb_extensions().extension_version
on a worker and asserts it matches the fork's commit short SHA (90dc1f24)
rather than the upstream build's. The expected value lives next to the
test with a comment pointing at DUCKLAKE_EXTENSION_TAG in the Dockerfiles
so the two move together.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>
0 commit comments