Skip to content

fix for duckdb v1.3.0 #25

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

Closed
wants to merge 3 commits into from
Closed

Conversation

abelcha
Copy link

@abelcha abelcha commented May 30, 2025

This PR addresses fixes related to duckdb v1.3.0, including fixes for parquet scan.

@lmangani
Copy link
Collaborator

lmangani commented May 30, 2025

Thanks for your contribution! In order for the builders to work we also need to update the MainDistributionPipeline action to the latest builder version. Could you allow edits by maintainers or update the pipeline as per example?

@abelcha
Copy link
Author

abelcha commented Jun 3, 2025

Thanks for your contribution! In order for the builders to work we also need to update the MainDistributionPipeline action to the latest builder version. Could you allow edits by maintainers or update the pipeline as per example?

I updated to v1.3.0 is that good ?

@lmangani
Copy link
Collaborator

lmangani commented Jun 3, 2025

Hi @abelcha absolutely and apologies for the delay here, i'm travelling till next week then we can make a release is that alright?

@lmangani
Copy link
Collaborator

lmangani commented Jun 5, 2025

@abelcha there's still an error in the workflow. Please allow edits my maintainers and we'll fix it

@lmangani
Copy link
Collaborator

lmangani commented Jun 7, 2025

To get this moving I merged your changes into #27 and resolved the issues there. Thanks!

@lmangani lmangani closed this Jun 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants