yihua commented on issue #713: URL: https://github.com/apache/hudi-rs/issues/713#issuecomment-5535891251
Follow-up on the four open items from the validation summary above; all four are resolved or in review: - **hudi-jvm-ffi publishing**: decided as not publishing for 0.5.0; #719 records the intent with `publish = false`. - **MSRV CI guard**: #721 adopts resolver v3 (MSRV-aware; a fresh resolution today is identical to v2's, verified) and adds an `msrv-check` job that compiles the workspace with the toolchain declared in `Cargo.toml`. The benchmark crates now inherit the workspace `rust-version` so the floor is uniform. - **datafusion extra pin**: #720 bounds the extra to the 54.x major instead of `==54.0.0` (resolves identically today; forward-looking). - **Wheel dry run on the untested targets**: done, and it caught a real publish blocker. Windows builds clean (37 MB wheel). The x86_64 macOS wheel fails compiling RocksDB at rustc's implicit 10.12 deployment floor (RocksDB uses C++17 aligned allocation, available from 10.13); this release is the first to compile the spill tier on that target, so the tagged publish would have failed mid-release. #722 sets the floor explicitly per target, verified by re-running the dry run: both mac targets and Windows now produce wheels (x86_64 41 MB, tag `macosx_10_13_x86_64`). With #719, #720, #721, and #722 in, the release branch can be cut with all known items closed. -- 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]
