chore: bump Ballista version to 54.0.0 - #2004
Merged
Merged
Conversation
andygrove
marked this pull request as ready for review
July 12, 2026 15:19
coderfender
pushed a commit
to coderfender/datafusion-ballista
that referenced
this pull request
Jul 13, 2026
* chore: bump Ballista version to 54.0.0 * chore: update python/Cargo.lock for 54.0.0
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
1 participant
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?
Part of #1977.
Rationale for this change
Preparing for the Ballista 54.0.0 release. DataFusion has already been upgraded to 54 on
main(#1906), so the next step in the release process is to bump the Ballista crate versions from 53.0.0 to 54.0.0 before cuttingbranch-54.What changes are included in this PR?
53.0.0to54.0.0via./dev/update_ballista_versions.py 54.0.0(crate versions and inter-crate path dependencies acrossballista-cli,ballista/{core,client,executor,scheduler},benchmarks,examples,python).Cargo.lock.Are there any user-facing changes?
Yes, the release version. No API changes.