What happens?
The vortex extension artifact for DuckDB v1.5.4 on windows_amd64 appears to be missing from the stable extension server.
The URL returns 404:
https://extensions.duckdb.org/v1.5.4/windows_amd64/vortex.duckdb_extension.gz
Why this matters
We package DuckDB extension artifacts for Python wheels in https://github.com/santosh-d3vpl3x/duckdb_extensions. During a full checksum refresh for the v1.5.4 release set, this artifact was the only missing vortex platform variant we observed.
A comparison check for another v1.5.4 platform did succeed, for example:
https://extensions.duckdb.org/v1.5.4/linux_amd64/vortex.duckdb_extension.gz
That suggests this is specific to the published windows_amd64 artifact rather than a broader release availability problem.
Reproduction
curl -I https://extensions.duckdb.org/v1.5.4/windows_amd64/vortex.duckdb_extension.gz
Expected: 200 OK with the extension artifact.
Actual: 404 Not Found.
Request
Could you confirm whether the windows_amd64 build for DuckDB v1.5.4 was intentionally skipped, or if the artifact is expected to be published to the stable extension server?
If it was intentionally omitted, a confirmation would help downstream package releases mark that platform/version combination unsupported.
What happens?
The
vortexextension artifact for DuckDBv1.5.4onwindows_amd64appears to be missing from the stable extension server.The URL returns 404:
Why this matters
We package DuckDB extension artifacts for Python wheels in https://github.com/santosh-d3vpl3x/duckdb_extensions. During a full checksum refresh for the
v1.5.4release set, this artifact was the only missingvortexplatform variant we observed.A comparison check for another
v1.5.4platform did succeed, for example:That suggests this is specific to the published
windows_amd64artifact rather than a broader release availability problem.Reproduction
Expected:
200 OKwith the extension artifact.Actual:
404 Not Found.Request
Could you confirm whether the
windows_amd64build for DuckDBv1.5.4was intentionally skipped, or if the artifact is expected to be published to the stable extension server?If it was intentionally omitted, a confirmation would help downstream package releases mark that platform/version combination unsupported.