NoahKusaba opened a new pull request, #2409:
URL: https://github.com/apache/datafusion-ballista/pull/2409
# Which issue does this PR close?
<!--
We generally require a GitHub issue to be filed for all bug fixes and
enhancements and this helps us generate change logs for our releases. You can
link an issue to this PR using the GitHub syntax. For example `Closes #123`
indicates that this PR will close issue #123.
-->
Closes #.
# Rationale for this change
Manifest-only cleanup. No resolved dependency or feature set changes.
- `[workspace.package]` gains `version`, `authors`, `license`, `homepage`,
`repository`; all ten members inherit. `readme` stays per-crate (inherited,
it resolves against the workspace root, not the crate).
- Internal crates moved to `[workspace.dependencies]`, so a release bump
touches one file. Five use sites keep the explicit `path` + `version` form
because Cargo rejects `default-features = false` on an inherited dep.
- Third-party stragglers now use the workspace table: `itertools`, `chrono`,
`axum`, `serde_json` (was declared 5x across 3 version specs), `tokio` in
benchmarks, and `serde` / `futures` / `tracing*` in ballista-cli. `reqwest`
is left alone: the CLI wants default TLS, chaos-testing deliberately drops
it.
- benchmarks was the only member hardcoding `edition` and omitting
`rust-version`; both now inherit. Dropped the executor's empty
`[dev-dependencies]` and `[build-dependencies]`.
- `python/Cargo.toml` moves to edition 2024, which needs Rust 1.85+, so
`rust-version` goes to 1.94.0. The old 1.82.0 floor was already unreachable
via `ballista = "=54.0.0"`. It can't inherit; it's in the workspace's
`exclude` list.
Verified: `cargo tree --all-features` identical across all 557 packages
before
and after; no `Cargo.lock` drift; `cargo check --workspace --all-targets
--locked` and the `--no-default-features` check pass; pyballista compiles
under
edition 2024; `taplo format --check` clean.
--
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]
