From 107c1b4a3001e0af4b0747b8bb023cd1365f8cd6 Mon Sep 17 00:00:00 2001 From: Xuanwo Date: Tue, 3 Mar 2026 22:53:32 +0800 Subject: [PATCH] ci: Use rust 2024 edition's default resolver instead We previously used `resolver=2` to enable feature unification. This functionality is now covered by the new `resolver=3`. Additionally, `resolver=3` is the default for the Rust 2024 edition and includes the valuable feature of MSRV-aware dependency resolution. I just remove our old `resolver=2` pin so we can use the edition's default. --- Cargo.toml | 10 ---------- 1 file changed, 10 deletions(-) diff --git a/Cargo.toml b/Cargo.toml index 1a02830b0b9f..be67d4dbe17d 100644 --- a/Cargo.toml +++ b/Cargo.toml @@ -47,16 +47,6 @@ members = [ "parquet_derive_test", ] -# Enable the version 2 feature resolver, which avoids unifying features for targets that are not being built -# -# Critically this prevents dev-dependencies from enabling features even when not building a target that -# uses dev-dependencies, e.g. the library crate. This in turn ensures that we can catch invalid feature -# flag combinations that would otherwise only surface in dependent crates -# -# Reference - https://doc.rust-lang.org/nightly/cargo/reference/features.html#feature-resolver-version-2 -# -resolver = "2" - exclude = [ # arrow-pyarrow-testing is excluded because it requires a Python interpreter with the pyarrow package installed, # which makes running `cargo test --all` fail if the appropriate Python environment is not set up.