Details
-
Improvement
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
Description
It would be good to test against DuckDB's dev branch to warn us if there are impending changes that break something.
While we're doing this, we should clean up some of the Currently some of our jobs do already https://github.com/apache/arrow/blob/f9f6fdbb7518c09b833cb6b78bc202008d28e865/ci/scripts/r_deps.sh#L45-L51
We should clean this up so that generally builds use the released DuckDB, but we can toggle dev DuckDB (and run a separate build that uses the dev DuckDB optionally)
Attachments
Issue Links
- links to