Skip to content

Main Extension Distribution Pipeline #436

Main Extension Distribution Pipeline

Main Extension Distribution Pipeline #436

Manually triggered June 5, 2026 15:28
Status Failure
Total duration 19m 11s
Artifacts 7

MainDistributionPipeline.yml

on: workflow_dispatch
Build extension binaries  /  Generate matrix
13s
Build extension binaries / Generate matrix
Matrix: Build extension binaries / linux
Matrix: Build extension binaries / macos
Matrix: Build extension binaries / wasm
Matrix: Build extension binaries / windows
Fit to window
Zoom out
Zoom in

Annotations

12 errors and 14 warnings
Build extension binaries / windows_amd64: duckdb/third_party/fmt/include/fmt/format.h#L336
inline variables require at least '/std:c++17'
Build extension binaries / windows_amd64: duckdb/third_party/fmt/include/fmt/format.h#L336
unrecognizable template declaration/definition
Build extension binaries / windows_amd64: duckdb/third_party/fmt/include/fmt/format.h#L327
'{': missing function header (old-style formal list?)
Build extension binaries / windows_amd64: duckdb/third_party/fmt/include/fmt/format.h#L327
unrecognizable template declaration/definition
Build extension binaries / windows_amd64: duckdb/third_party/fmt/include/fmt/format.h#L326
syntax error: identifier 'checked_array_iterator'
Build extension binaries / windows_amd64: duckdb/third_party/fmt/include/fmt/format.h#L326
'stdext': is not a class or namespace name
Build extension binaries / windows_amd64_mingw
The strategy configuration was canceled because "duckdb-stable-build.windows.windows_amd64_windows-202" failed
Build extension binaries / windows_amd64_mingw
The operation was canceled.
Build extension binaries / Generate matrix
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-go@v5. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Build extension binaries / linux_amd64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/cache/save@v4, actions/checkout@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Build extension binaries / linux_arm64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/cache/save@v4, actions/checkout@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Build extension binaries / osx_arm64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-python@v5, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Build extension binaries / osx_arm64
ninja 1.13.2 is already installed and up-to-date. To reinstall 1.13.2, run: brew reinstall ninja
Build extension binaries / osx_amd64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-python@v5, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Build extension binaries / osx_amd64
ninja 1.13.2 is already installed and up-to-date. To reinstall 1.13.2, run: brew reinstall ninja
Build extension binaries / windows_amd64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-python@v5, lukka/run-vcpkg@v11.1. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Build extension binaries / windows_amd64
The file vcpkg.json was found multiple times with glob expression '**/vcpkg.json'.
Build extension binaries / windows_amd64_mingw
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-python@v5, lukka/run-vcpkg@v11.1. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Build extension binaries / windows_amd64_mingw
The file vcpkg.json was found multiple times with glob expression '**/vcpkg.json'.
Build extension binaries / wasm_threads
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4, emscripten-core/setup-emsdk@v13. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Build extension binaries / wasm_eh
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4, emscripten-core/setup-emsdk@v13. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Build extension binaries / wasm_mvp
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4, emscripten-core/setup-emsdk@v13. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Artifacts

Produced during runtime
Name Size Digest
httpserver-v1.4-andium-extension-linux_amd64
13.6 MB
sha256:04a6643062d91e066d297cb2dd23896056fca6b29df13f258c0961600c573b08
httpserver-v1.4-andium-extension-linux_arm64
12.8 MB
sha256:bb10b086388fc31487f549eae3556bd5c53ad655435c8606762724b1ea82f77b
httpserver-v1.4-andium-extension-osx_amd64
9.83 MB
sha256:9cd4d69ca15be82b27169def871bce6084f881a5073f42c378a2a7d4452074a9
httpserver-v1.4-andium-extension-osx_arm64
9.27 MB
sha256:3c9089dd56b60078749d2f0ee57301ac17f7a8c1b33fa63dd87cc91ce5537898
httpserver-v1.4-andium-extension-wasm_eh
91.4 KB
sha256:d698be4b6d5508bd34963a242791351a5736d375e44d4c1ff5d06345946b2a51
httpserver-v1.4-andium-extension-wasm_mvp
84.3 KB
sha256:1492e5cf627a905c542216260653edca12731b13f6d98fff732dd8babe7feebd
httpserver-v1.4-andium-extension-wasm_threads
84.3 KB
sha256:d1fc1f4c4f42cf7093f5ffb43618f29bd5b7ea2431c980aa0f34e6aa400310c5