This is an automated email from the ASF dual-hosted git repository.
Jefffrey pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/arrow-rs.git
The following commit(s) were added to refs/heads/main by this push:
new 3c938dd8d5 chore: bump resolver to v3 (#10460)
3c938dd8d5 is described below
commit 3c938dd8d5d5ce6aa8f3e87c940654382ee1bd5e
Author: Jeffrey Vo <[email protected]>
AuthorDate: Tue Aug 4 11:21:19 2026 +0900
chore: bump resolver to v3 (#10460)
v3 should supersede v2 (and adds extra feature)
-
https://doc.rust-lang.org/cargo/reference/resolver.html#resolver-versions
Unfortunately even though v3 is the default in edition 2024, we still
need to specify it manually since the setting doesn't play well with
virtual workspaces 😔
---
Cargo.toml | 14 +++++---------
1 file changed, 5 insertions(+), 9 deletions(-)
diff --git a/Cargo.toml b/Cargo.toml
index 28acc4125f..b6042a5f26 100644
--- a/Cargo.toml
+++ b/Cargo.toml
@@ -47,15 +47,11 @@ 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"
+# This is the default for edition 2024 but we must manually specify it for
virtual
+# workspaces.
+# - https://github.com/rust-lang/cargo/issues/10112
+# - https://github.com/rust-lang/cargo/issues/10587
+resolver = "3"
exclude = [
# arrow-pyarrow-testing is excluded because it requires a Python
interpreter with the pyarrow package installed,
