Dandandan opened a new pull request, #2311:
URL: https://github.com/apache/datafusion-ballista/pull/2311
## Which issue does this PR close?
N/A
## Rationale for this change
The workspace `rust-version` was pinned at 1.94.0. This raises it to 1.97.1,
the current stable release.
## What changes are included in this PR?
A single line in the root `Cargo.toml`: `rust-version = "1.94.0"` ->
`"1.97.1"`. All member crates pick it up through `rust-version = { workspace =
true }`.
`dev/msrvcheck` only asserts that the project MSRV is **at least** that of
the DataFusion dependencies, so raising it stays compatible.
Note that the comment above the field says *"we should try to follow
datafusion version"*. Moving straight to latest stable means the repo no longer
tracks DataFusion's MSRV and will reject contributors on older toolchains —
happy to pin to whatever DataFusion 55 declares instead if that is preferred.
`python/Cargo.toml` is left at `rust-version = "1.82.0"`: it is excluded
from the workspace, is edition 2021, and builds against the published `ballista
=54.0.0` from crates.io, so its MSRV describes the released crates rather than
this tree.
## Are these changes tested?
`ci/scripts/rust_clippy.sh` passes clean on 1.97.1 — all eight `cargo clippy
--all-targets ... -- -D warnings` invocations, including both `ballista-cli`
feature combinations. No clippy fixes were needed.
## Are there any user-facing changes?
Yes — the minimum supported Rust version rises from 1.94.0 to 1.97.1.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
