-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Extension status toward v1.2.0 #259
Comments
@carlopi thanks for doing this! |
@rustyconover, great, adapted the table to after your PRs. |
@lmangani, @queryproc, @Dtenwolde, @isaacbrodsky, @ywelsch, @hannes, @archiewood, @hafenkran, @JAicewizard, @pdet, @gropaul, @Alex-Monahan, @Maxxen, @freddie-freeloader This issue might be relevant to have a look. Basically, we are are doing some preparatory work for v1.2.0, above some checks we performed on current status and some of the major changes / how to get ready. Thanks a lot! |
Just updated the above table, some have been fixed in the meantime, nice. |
I have been able to track down the muslc and widows version. Musclc is broken because duckdb/extension-ci-tools#135, and windows fixed in a local branch already. Once the alpine runs are fixed I can merge my windows fix, and make a PR here to bump |
Thanks for creating this issue! The musl issue for duckpgq has been fixed here. I'll merge duckdb 1.2.0 with duckdb-pgq on release day probably |
Opening this issue to track status of community extensions moving towards release v1.2.0, that will happen later this month.
Current status looks great to me, many extensions are already compatible with both versions and require no changes, some are having problem in selected platforms (possible way forward is disable them) and others are incompatible with current duckdb main branch.
Relevant changes in platforms
windows_amd64_rtools
has been renamedwindows_amd64_mingw
linux_amd64_musl
platform has been added (might be disabled viaexcluded_platforms: linux_amd64_musl
if not workable)Recommended path forward
If extension works already, great. No required action.
If there are problems in selected platforms, consider skipping them via
excluded_platforms: "platform_name"
._musl
problems connected to rust toolchains most likely require a general fix. We might consider disabling unsupported platforms automatically.If there are incompatibilities due to duckdb source code changes, provide a
ref_next
in the extension descriptor, see https://duckdb.org/community_extensions/development#how-to-maintain-an-extension-through-duckdb-releases.On changing a descriptor for an extension CI is run both for latest stable release (
v1.1.3
) and for current main.You could use that to double check the status of your extension.
Note that extensions that on release day compile and tests successfully will be automatically available to users on duckdb updates.
This is a plus / nice to have, but NOT a requirement.
Extensions that can't be built on the release hash will be made available as soon as successful update of the extension descriptor.
Note that after
v1.2.0
lands, extensions will stop to receive updates forv1.1.3
, andv1.2.0
will be considered the latest stable release.Thanks everyone.
Please do open issues to duckdb/community-extensions or discuss at https://discord.duckdb.org, looking forward to improve this.
Help is also welcome, especially if you want to help fellow or new extension developers.
One area that could use more love if for example improving the documentation on how to develop extensions.
That's hosted at https://duckdb.org/community_extensions/development, feel free to send improvements to the files in the community_extensions folder to duckdb/duckdb-web.
Current status as of 28 January 2025
CI run: https://github.com/duckdb/community-extensions/actions/runs/12685119358/job/35355040692
httpfs
, see example fix hereCurrent status as of 10 January 2025
CI run: https://github.com/duckdb/community-extensions/actions/runs/12685119358/job/35355040692
httpfs
, see example fix hereExcept of some build problems (most likely due to changes in APIs duckdb-side)
bigquery
https://github.com/duckdb/community-extensions/actions/runs/12685119358/job/35355064200#step:17:10024
datasketches
https://github.com/duckdb/community-extensions/actions/runs/12685119358/job/35354989255#step:17:2113
duckpgq
https://github.com/duckdb/community-extensions/actions/runs/12685119358/job/35354998020
scrooge
https://github.com/duckdb/community-extensions/actions/runs/12685119358/job/35355040043#step:17:311
shellfs
https://github.com/duckdb/community-extensions/actions/runs/12685119358/job/35355028445
The text was updated successfully, but these errors were encountered: