Notify existing Community Extensions of changed API

[samansmink]

The updated extension API entrypoint from DuckDB v1.4 will require some work from many community extension maintainers. We'll automatically create an issue in the affected repositories pointing to this issue.

The easiest way to understand what needs to change is to look at the extension template PR that applies the changes.

If you want to prepare your extension before the DuckDB v1.4.0 is out, check out this example on how to use ref_next in the PR where the quack extension is bumped: https://github.com/duckdb/community-extensions/pull/548

[dentiny]

Thanks for the notification!

[haydenflinner]

Is this update what has left the prql extension behind? Not having any success using it from the wasm console. Installing locally gives:

INSTALL prql FROM community;
HTTP Error:
Failed to download extension "prql" at URL "http://community-extensions.duckdb.org/v1.4.0/osx_arm64/prql.duckdb_extension.gz" (HTTP 403)

Candidate extensions: "parquet", "mysql", "sqlite", "sqlite3", "mysql_scanner"
For more info, visit https://duckdb.org/docs/stable/extensions/troubleshooting?version=v1.4.0&platform=osx_arm64&extension=prql