Skip to content

Main Extension Distribution Pipeline #444

Main Extension Distribution Pipeline

Main Extension Distribution Pipeline #444

Manually triggered June 12, 2026 15:41
Status Failure
Total duration 31m 18s
Artifacts 7

MainDistributionPipeline.yml

on: workflow_dispatch
Build extension binaries  /  Generate matrix
30s
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 / 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_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/
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 / 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 / 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

Artifacts

Produced during runtime
Name Size Digest
httpserver-v1.4-andium-extension-linux_amd64
13.6 MB
sha256:e0f7bce791afd05eb9822b8269c2870ac542807e3ac1372113667a9863e38ccb
httpserver-v1.4-andium-extension-linux_arm64
12.8 MB
sha256:4b44524a61d3867c7b447cf2f8953b21330bd14ceb53ceaac8fd55758b1eee60
httpserver-v1.4-andium-extension-osx_amd64
9.84 MB
sha256:c61098977ae7c899972ef231f1f9f4679d0ea72194c668427dc7159aa9da232b
httpserver-v1.4-andium-extension-osx_arm64
9.27 MB
sha256:82cdfbf10bf93603fadc5df43f3ca2892490154ca9c7c15e7766e42a28df6a46
httpserver-v1.4-andium-extension-wasm_eh
91.4 KB
sha256:e8e0464bd5d3e4362ec71058d4531a7e8b9fbace0b80c33b353bf04a96ef01a5
httpserver-v1.4-andium-extension-wasm_mvp
84.3 KB
sha256:f8dc4e8e64bfbd8ed37db6299cbf3ac0039741cdd498f02b1eb7b85a9bc031dd
httpserver-v1.4-andium-extension-wasm_threads
84.3 KB
sha256:969e046662cd0c57ca6e0092b2a58b102db5daa4db271a3ace10d31971b167a5