Skip to content

chore: pin DataFusion to 56.0.0-rc2 - #2910

Draft
andygrove wants to merge 1 commit into
apache:mainfrom
andygrove:andygrove/datafusion-56.0.0-rc2
Draft

andygrove wants to merge 1 commit into
apache:mainfrom
andygrove:andygrove/datafusion-56.0.0-rc2

Conversation

@andygrove

Copy link
Copy Markdown
Member

Which issue does this PR close?

No issue. This is the next step of the DataFusion 56 upgrade, following #2718, which pinned 56.0.0-rc1.

Rationale for this change

DataFusion 56.0.0-rc2 is the current release candidate. Testing Ballista against it before the release ships means problems turn up early. The 56.0.0 release tag points at the same commit as rc2 (7e7ae72a). The crates are not on crates.io yet, so the pin stays a git tag for now.

The changes from rc1 to rc2 are three backports on branch-56:

What changes are included in this PR?

  • Move the DataFusion git dependencies in Cargo.toml from tag 56.0.0-rc1 to 56.0.0-rc2.
  • Update Cargo.lock to match.

No code changes were needed. The vendored DataFusion protos are unchanged and dev/update_datafusion_proto.py --check passes.

Are there any user-facing changes?

No.

🤖 Generated with Claude Code

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@andygrove
andygrove marked this pull request as draft November 22, 2026 14:57
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.

1 participant