Consider updating vcpkg baseline to support newer packages

[brannn]

The current vcpkg baseline (April 2025, commit ce613c41372b23b1f51333815feb3edd87ef8a8b) is missing some newer package versions.

I am developing a DuckDB extension for querying Universal Scene Description (USD) files that I plan to submit to the community extensions repository. This extension requires OpenUSD 25.8 (released October 2025), which is not available in the current baseline.

Suggested vcpkg commit: e9b9012b4eea442947623fa7811aaa6c8ab7fde4 (October 2025)

This would benefit extensions requiring newer dependency versions while maintaining backwards compatibility (vcpkg_commit is an optional override parameter).

For now, I've overridden vcpkg_commit in my workflow to unblock development, but this means the extension won't build in the official community extension pipeline without a similar override.

[samansmink]

Hey @brannn thanks for the issue, a vcpkg bump to latest stable vcpkg version is scheduled for the upcoming DuckDB v1.5 release.

[rustyconover]

In your extension's vcpkg.json you can do an explicit overlay for a package. See what I'm doing in datasketches for an example.

[JAicewizard]

You can manually specify a vcpkg commit!

In fact you can even specify a custom vcpkg repository!

name: Main Extension Distribution Pipeline
on:
  push:
  pull_request:
  workflow_dispatch:

concurrency:
  group: ${{ github.workflow }}-${{ github.ref }}-${{ github.head_ref || '' }}-${{ github.base_ref || '' }}-${{ github.ref != 'refs/heads/main' || github.sha }}
  cancel-in-progress: true

jobs:
  duckdb-stable-build:
    name: Build extension binaries
    uses: duckdb/extension-ci-tools/.github/workflows/_extension_distribution.yml@v1.4.3
    with:
      duckdb_version: v1.4.2
      ci_tools_version: v1.4.3
      extension_name: faiss
      vcpkg_url: "https://github.com/microsoft/vcpkg.git"
      vcpkg_commit: 54760c3439fa2fdf2f42ccd730fcf2639c3fe101
      exclude_archs: "wasm_mvp;wasm_eh;wasm_threads"
      build_duckdb_shell: false
      extra_toolchains: "fortran;omp"

Unfortunatly the combination does not always work, on mingw windows specifying both a custom repo and commit breaks git. (Instead of debuging this I just used overlay ports instead)

[rustyconover]

Doing so breaks the One Definition Rule (ODR)

In C++ (and to some extent in C), the ODR says that each function, global variable, or type must have exactly one definition across the entire program. Violating this can lead to undefined behavior, even if the code compiles.

If a user wants to use the same dependency in multiple extensions if you link in different versions (as what would happen if you override vcpkg_commit) things are going to go pear-shaped quickly.

[brannn]

@rustyconover Thanks for this. Overlay approach is definitely more surgical than overriding the entire vcpkg baseline. But it does mean carrying port files in the repo and cleaning them up once the upstream baseline catches up. No urgency to release this, so I'll just wait for the v1.5 baseline update.

[rustyconover]

Carrying port files in the repo isn't terrible. They're typically quite small.

It comes down to your particular amount of faith in upstream maintainers. My mileage has varied.

[JAicewizard]

Doing so breaks the One Definition Rule (ODR)

two extensions using the same package would violate this rule, whether the versions match or not. You could end up with 2 of the same global variables for example. Ive had issues with this in testing, where the extension used to be linked statically and dynamically, giving UB.

Using overlay ports is generally better, but it depends on what you need.