You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Adding support for extension authors to add minimum supported DuckDB version for the extension would be nice. Even better, if this could be automatically generated that'd be great.
When trying to add support for the new gsheet extension for customers we were running into this error:
HTTP Error: Failed to download extension "gsheets" at URL "http://community-extensions.duckdb.org/v1.1.1/<PLATFORM>/gsheets.duckdb_extension.gz" (HTTP 403)
Candidate extensions: "postgres", "inet", "https", "delta", "s3"
We had duckdb (and Rust bindings) pinned at v1.1.11 and were running into this issue with INSTALL gsheets FROM community;.
It would be nice if there was a notice somewhere for an extension that would let users know what minimum version of DuckDB they need. Maybe this metadata could also inform a more helpful HTTP error message indicating that you need to upgrade.
To be fair, the Github repo for the repository did mention that v1.1.3 is supported but it didn't say only v1.1.3 is supported. Also it would be hard to pull from that for CI unlike a dedicated field in a YAML file.
Footnotes
Rust bindings with bundled libducksys are behind and do not have versions v1.1.2 or v1.1.3 yet ↩
The text was updated successfully, but these errors were encountered:
On Wed, Jan 15, 2025 at 13:09 Michael Harris ***@***.***> wrote:
Adding support for extension authors to add minimum supported DuckDB
version for the extension would be nice. Even better, if this could be
automatically generated that'd be great.
When trying to add support for the new gsheet extension
<https://duckdb.org/community_extensions/extensions/gsheets.html> for
customers we were running into this error:
HTTP Error: Failed to download extension "gsheets" at URL "http://community-extensions.duckdb.org/v1.1.1/<PLATFORM>/gsheets.duckdb_extension.gz" (HTTP 403)
Candidate extensions: "postgres", "inet", "https", "delta", "s3"
We had duckdb (and Rust bindings) pinned at v1.1.11
<#m_-7818785032269341540_user-content-fn-1-5f8fc69e3f39a22da45e2b251599c71a>
and were running into this issue with INSTALL gsheets FROM community;.
It would be nice if there was a notice somewhere for an extension that
would let users know what minimum version of DuckDB they need. Maybe this
metadata could also inform a more helpful HTTP error message indicating
that you need to upgrade.
To be fair, the Github repo for the repository did mention that v1.1.3 is
supported but it didn't say *only* v1.1.3 is supported. Also it would be
hard to pull from that for CI unlike a dedicated field in a YAML file.
Footnotes
1.
Rust bindings with bundled libducksys are behind and do not have
versions v1.1.2 or v1.1.3 yet ↩
<#m_-7818785032269341540_user-content-fnref-1-5f8fc69e3f39a22da45e2b251599c71a>
—
Reply to this email directly, view it on GitHub
<#271>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAFSWJOTE6PGCZKK45H4OWL2K2P6RAVCNFSM6AAAAABVH2XVAOVHI2DSMVQWIX3LMV43ASLTON2WKOZSG44TANJRGUYTGNI>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
Adding support for extension authors to add minimum supported DuckDB version for the extension would be nice. Even better, if this could be automatically generated that'd be great.
When trying to add support for the new gsheet extension for customers we were running into this error:
We had
duckdb
(and Rust bindings) pinned at v1.1.11 and were running into this issue withINSTALL gsheets FROM community;
.It would be nice if there was a notice somewhere for an extension that would let users know what minimum version of DuckDB they need. Maybe this metadata could also inform a more helpful HTTP error message indicating that you need to upgrade.
To be fair, the Github repo for the repository did mention that v1.1.3 is supported but it didn't say only v1.1.3 is supported. Also it would be hard to pull from that for CI unlike a dedicated field in a YAML file.
Footnotes
Rust bindings with bundled libducksys are behind and do not have versions v1.1.2 or v1.1.3 yet ↩
The text was updated successfully, but these errors were encountered: