Repository navigation
Release DataFusion 52.5.0 (minor) Release (Apr 2026) #21078
Description
Activity
@alamb : Can we add the following issues to this release please?
I'll plan to make a RC next week hopefully
Reacted by Matt Butrovich, feniljain and Haresh KhannaI went through the list of commits on main and found some panics / regressions i think would be good to fix on branch-52 and added them to this list.
Reacted by Haresh Khanna- changed the title
[-]Release DataFusion 52.5.0 (minor/) Release (Apr 2026)[/-][+]Release DataFusion 52.5.0 (minor) Release (Apr 2026)[/+]on Apr 4, 2026 Note: #20048 does not affect branch-52 (the affected code is only present in main).
I am only going to backport PRs that look like they are regressions / serious issues
I think #20900 also doesn't apply to 52
Note: #20900 is not applicable to branch-52 (requires changes that got added in branch-53, not main)
Note: #20306 was dropped from the release as it does not apply cleanly and the fix still panics on branch-52.
I think this would be nice to include #21155 I think we have a branch resolving it on top of 52.3 we were using internally https://github.com/rerun-io/arrow-datafusion/tree/tsaucer/52.3.0-inner-ffi
#21155 / @timsaucer / [TODO BACKPORT PR]
I think this would be nice to include #21155 I think we have a branch resolving it on top of 52.3 we were using internally
Thanks -- added!
6 remaining items
#21439 for the FFI issue
Reacted by NickReacted by Andrew LambReacted by Andrew Lamb- added a commit that references this issue
on Apr 7, 2026 Ok, we have the content in.
I updated the version bump / changelog
Once that is good I'll move on to making a release candidate
- added a commit that references this issue
on Apr 7, 2026 I made an RC and started a vote: https://lists.apache.org/thread/scnnmsw6g200ckjj1rgx58oj9q6xzb2h
- added a commit that references this issue
on Apr 9, 2026 The release was approved and has been released to crates.io: https://lists.apache.org/thread/kl19synnmoj4z7mhlf3mywox9pvnn0w8
Thank you everyone who helped
- added a commit that references this issue
on Apr 14, 2026
Is your feature request related to a problem or challenge?
I strongly suspect we'll end up with a few more bugs on the
branch-52release, so I am proactively opening a ticket to propose / track such a releaseSteps:
Content:
Requested Bug Fixes. Format: Issue / Requester / Backport PR