ci: build and test v2.0 against Haybarn 2.0 rc9 and vgi.v3 fixtures

The distribution pipeline still built against haybarn-v1.5.5-rc1 with the
1.5 ci-tools, so every 2.0 build failed on 2.0-only engine headers. Use
haybarn-v2.0.0-rc9 with ci-tools haybarn-2.0, as the community 2.0 lane does.

The integration suite cloned vgi-python's default branch, whose fixture
workers host only vgi.v2, so ATTACH failed with ProtocolNotSupportedError.
Default the fixtures to the vgi.v3 SDK release v0.48.0.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Author: rustyconover

.github/workflows/MainDistributionPipeline.yml

@@ -36,26 +36,29 @@ jobs:
 
   duckdb-stable-build:
     name: Build extension binaries
-    uses: Query-farm-haybarn/haybarn-extension-ci-tools/.github/workflows/_extension_distribution.yml@haybarn
+    # The v2.0 branch builds against the Haybarn 2.0 engine with the 2.0 line of
+    # the Haybarn ci-tools fork, the same pairing as the community haybarn-2.0
+    # lane. Keep duckdb_version in lockstep with the duckdb submodule's tag.
+    uses: Query-farm-haybarn/haybarn-extension-ci-tools/.github/workflows/_extension_distribution.yml@haybarn-2.0
     secrets:
       vcpkg_token: ${{ secrets.HAYBARN_VCPKG_TOKEN }}
+      VCPKG_CACHING_AWS_ACCESS_KEY_ID: ${{ secrets.HAYBARN_BUILD_CACHE_R2_ACCESS_KEY_ID }}
+      VCPKG_CACHING_AWS_SECRET_ACCESS_KEY: ${{ secrets.HAYBARN_BUILD_CACHE_R2_SECRET_ACCESS_KEY }}
+      VCPKG_CACHING_AWS_ENDPOINT_URL: ${{ secrets.R2_ENDPOINT }}
     with:
-      duckdb_version: haybarn-v1.5.5-rc1
-      ci_tools_version: haybarn
+      duckdb_version: haybarn-v2.0.0-rc9
+      ci_tools_version: haybarn-2.0
+      override_duckdb_repository: 'https://github.com/Query-farm-haybarn/haybarn'
       override_ci_tools_repository: 'Query-farm-haybarn/haybarn-extension-ci-tools'
       extension_name: vgi
-      # This artifact is not consumed and is consistently the slowest matrix
-      # leg (roughly 20 minutes even with warm vcpkg and ccache state).
-      exclude_archs: 'windows_amd64_mingw'
-      use_prebuilt_images: true
-      use_prebuilt_wasm_image: true
+      # wasm_mvp, osx_amd64 and windows_arm64 are not built on the 2.0 line.
+      # windows_amd64_mingw is not consumed and is consistently the slowest
+      # matrix leg (roughly 20 minutes even with warm vcpkg and ccache state).
+      exclude_archs: 'wasm_mvp;osx_amd64;windows_arm64;windows_amd64_mingw'
+      # vcpkg release 2026.06.24, the 2.0-line pin.
+      vcpkg_commit: 'cd61e1e26a038e82d6550a3ebbe0fbbfe7da78e3'
       # The embedded Iroh connector is compiled from the pinned Rust source as
-      # part of the extension, so both native Linux and WASM builders need the
-      # prebuilt image variants that contain Cargo. `extra_toolchains` controls
-      # inline image builds, but does not alter an already-published image.
-      image_variant: rust
-      wasm_image_variant: rust
-      prebuilt_image_tag: v1.5.5
+      # part of the extension, so the builders need Cargo.
       extra_toolchains: parser_tools;rust
       # NOTE: this pipeline does NOT run the VGI integration suite.
       #

.github/workflows/integration.yml

@@ -42,7 +42,9 @@ jobs:
     env:
       VGI_INSTALL_FIXTURES: "1"
       VGI_FIXTURES_DIR: /tmp/vgi-python
-      VGI_FIXTURES_REF: ${{ inputs.fixtures_ref }}
+      # v2.0 speaks vgi.v3; vgi-python's default branch still hosts vgi.v2 until
+      # the 0.48.0 release (vgi-python#98) merges, so pin the v3 SDK release.
+      VGI_FIXTURES_REF: ${{ inputs.fixtures_ref || 'v0.48.0' }}
       GEN: ninja
       BUILD_VGI_FILTER_V2_TESTS: "1"
       USE_MERGED_VCPKG_MANIFEST: "1"