Repository navigation
chore: bump Ballista version to 56.0.0 - #2906
Merged
Merged
Conversation
Also add ballista-flight-sql to dev/update_ballista_versions.py, which previously left it at the old version. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Which issue does this PR close?
N/A. This is part of preparing the 56.0.0 release.
Rationale for this change
DataFusion 56 is about to be released, and Ballista 56.0.0 will follow it. The crate versions need to move to 56.0.0 ahead of the release.
What changes are included in this PR?
dev/update_ballista_versions.py 56.0.0to bump the workspace version and the versions of the Ballista crates' dependencies on each other, and updatedCargo.lock.ballista-flight-sqltodev/update_ballista_versions.py. The script did not know about it, so it would have stayed at 55.0.0.The Python client is versioned and released separately and still builds against the DataFusion 55 release of
datafusion-python, so it is not changed here. It will move to 56 oncedatafusion-python56 is released.integrations/icebergdepends on a pinned Ballista git revision and is not changed here.The DataFusion dependency is still pinned to the 56.0.0-rc1 tag. Switching to the released crates will be a separate PR once DataFusion 56.0.0 is published.
Are there any user-facing changes?
Crate versions change from 55.0.0 to 56.0.0. Because the client and scheduler check that their major versions match, 56.0.0 clients will not work with 55.x schedulers, which is the expected behavior.
🤖 Generated with Claude Code