andygrove opened a new pull request, #7169: URL: https://github.com/apache/datafusion-comet/pull/7169
## Which issue does this PR close? N/A. This is the proposed "Refresh Dependencies in main" release process step (added to `release_process.md` in #7166), done at the start of the 1.3.0 cycle after `branch-1.2` was cut. ## Rationale for this change Nothing refreshes the third-party entries in the lockfiles as a whole. Dependabot covers only `native/`, groups minor and patch updates, and does not touch transitive dependencies or `contrib/delta/native`. Landing the refresh right after the release branch is cut gives the new versions the whole development cycle of nightly and merge queue runs before the next cut, while `branch-1.2` keeps the lockfile it was cut with. ## What changes are included in this PR? `cargo update` in `native/` and in `contrib/delta/native/`. Only the two `Cargo.lock` files change; no `Cargo.toml` is touched. - `native/Cargo.lock`: 150 packages change, `tinyvec_macros` is dropped, and a fourth `quick-xml` (0.42.0) appears, pulled in by `reqsign-aws-core` 3.2.0. The `iceberg-rust` git pin and the `datafusion*` crates stay where they are. - `contrib/delta/native/Cargo.lock`: 57 packages change, with none added or removed. The ones that matter most: - Arrow and Parquet patch releases: `arrow*` and `parquet*` 59.3.0 -> 59.3.1. Parquet 60.0.0 is available and is a manual bump. - `tokio` 1.53.1 -> 1.54.1, `tokio-util` 0.7.19 -> 0.7.20. - The S3 credential path: `aws-config` 1.12.0 -> 1.13.0 and the other `aws-*` and `aws-smithy-*` crates, plus the `reqsign-*` crates (`reqsign-core` 3.3.1 -> 3.3.2, `reqsign-aws-core` 3.1.1 -> 3.2.0, `reqsign-aws-v4` 3.3.0 -> 3.3.1, `reqsign-azure-storage` 3.2.1 -> 3.3.0, `reqsign-google` 3.1.1 -> 3.2.0, `reqsign-aliyun-oss` 3.1.5 -> 3.2.0). - TLS and networking: `rustls` 0.23.45 -> 0.23.46, `rustls-webpki` 0.103.15 -> 0.103.16, `quinn` 0.11.11 -> 0.11.12, `hyper` 1.11.1 -> 1.12.0. - `zstd` 0.14.0 -> 0.14.3, `uuid` 1.26.1 -> 1.29.0, `serde_json` 1.0.151 -> 1.0.154, `jiff` 0.2.35 -> 0.2.38. ## How are these changes tested? On macOS against the new lockfiles: - `cargo clippy --all-targets --workspace --locked -- -D warnings` in `native/` is clean. - `cargo check --all-targets --locked` in `contrib/delta/native/` passes. - `cargo test --workspace --locked --no-fail-fast` in `native/`: `spark-expr` (1287), `shuffle` (190), `operators` (42), `common` (72), `proto` (4) and `comet-udf-sdk` pass; the `comet` lib passes 953 with 5 failures. - The 5 failures are `parquet::objectstore::http_metrics::tests::*`, which bind `127.0.0.1:0` and get `PermissionDenied` in my sandbox, so they did not run here. The `reqsign` and `aws-*` bumps are in the area they exercise, so I am relying on CI for them. - 4 `datafusion-comet-jni-bridge` tests (`errors::tests::error_from_panic`, `jint_array_panic_exception`, `jlong_panic_exception`, `shuffle_size_limit_survives_datafusion_wrappers_and_jni`) fail the same way with the old lockfile (`assertion failed: env.exception_check()`), so the refresh does not cause them. The JVM-side suites are what run the refreshed `libcomet`, so this PR needs the labels that opt it into the suites the PR tier skips (`run-all-spark-profiles`, `run-iceberg-tests`, `run-delta-tests`). -- 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]
