Skip to content

chore: formally bump DataFusion requirement to 55.1, too - #79

Merged
lidavidm merged 1 commit into
mainfrom
dev
Oct 2, 2026
Merged

lidavidm merged 1 commit into
mainfrom
dev

Conversation

@lidavidm

Copy link
Copy Markdown
Contributor

No description provided.

@lidavidm

Copy link
Copy Markdown
Contributor Author

CC @Mandukhai-Alimaa - we can't fully trust Dependabot upgrades; it didn't seem to update Cargo.toml. Also it will try to update dependencies that are pinned by DataFusion which breaks things too (#77) so we have to be careful

@lidavidm
lidavidm marked this pull request as ready for review September 29, 2026 07:02

@Mandukhai-Alimaa Mandukhai-Alimaa left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we pin driverbase to a specific revision? Regenerating Cargo.lock advanced it from c4f4114 to f358b4d. That revision allows Arrow >=59.3,<61, so Cargo selected Arrow 60 for driverbase. DataFusion 55.1 constrains Arrow to the 59.x line, which resolves to 59.3 here, resulting in incompatible duplicate Arrow types.

@lidavidm

lidavidm commented Oct 2, 2026

Copy link
Copy Markdown
Contributor Author

Hmm, I wonder why Cargo doesn't combine the constraints...

@lidavidm

lidavidm commented Oct 2, 2026

Copy link
Copy Markdown
Contributor Author

@lidavidm
lidavidm merged commit 2b2985a into main Oct 2, 2026
14 checks passed
@lidavidm
lidavidm deleted the dev branch October 2, 2026 03:25
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