alamb opened a new pull request, #13801: URL: https://github.com/apache/datafusion/pull/13801
## Which issue does this PR close? Part of - https://github.com/apache/datafusion/pull/13663 ## Rationale for this change I needed to update Cargo.lock in `datafusion-cli` as part of https://github.com/apache/datafusion/pull/13663 and I hit some MSRV problem related to home I wanted to fix it in a separate PR rather than try and include it as part of the arrow upgrade. When I did `cargo update` in the datafusion-cli directory, the MSRV check fails: Specifically, home 0.5.11 has a MSRV of `1.81` which is too new to pass our CI check -- Updating home v0.5.9 -> v0.5.11 ``` andrewlamb@Andrews-MacBook-Pro-2:~/Software/datafusion2/datafusion-cli$ cargo msrv verify [Meta] cargo-msrv 0.17.1 Compatibility Check #1: Rust 1.80.1 [FAIL] Is incompatible ╭────────────────────────────────────────────────────────────────────────╮ │ error: rustc 1.80.1 is not supported by the following package: │ │ home@0.5.11 requires rustc 1.81 │ │ Either upgrade rustc or select compatible dependency versions with │ │ `cargo update <name>@<current-ver> --precise <compatible-ver>` │ │ where `<compatible-ver>` is the latest version supporting rustc 1.80.1 │ ╰────────────────────────────────────────────────────────────────────────╯ Crate source was found to be incompatible with Rust version '1.80.1' specified as MSRV in the Cargo manifest located at '/Users/andrewlamb/Software/datafusion2/datafusion-cli/Cargo.toml' ``` ## What changes are included in this PR? 1. Pin `home` to `0.5.9` 2. `cargo update` in `datafusion-cli` 3. Check in the result <!-- There is no need to duplicate the description in the issue here but it is sometimes worth providing a summary of the individual changes in this PR. --> ## Are these changes tested? <!-- We typically require tests for all PRs in order to: 1. Prevent the code from being accidentally broken by subsequent changes 4. Serve as another way to document the expected behavior of the code If tests are not included in your PR, please explain why (for example, are they covered by existing tests)? --> ## Are there any user-facing changes? <!-- If there are user-facing changes then we may require documentation to be updated before approving the PR. --> <!-- If there are any breaking changes to public APIs, please add the `api change` label. --> -- 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: github-unsubscr...@datafusion.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: github-unsubscr...@datafusion.apache.org For additional commands, e-mail: github-h...@datafusion.apache.org
