From e9fd9b78f126b264e47cb643cc25c5730d2d7cff Mon Sep 17 00:00:00 2001 From: Yin Lin Date: Wed, 29 Jul 2026 22:45:41 +0000 Subject: [PATCH] build: bump abseil-cpp to 20260526.0 for torch_tpu compatibility torch_tpu main moved to abseil-cpp 20260526.0, whose BCR entry carries a different bzlmod compatibility level than older releases, so raiden's 20260107.1 pin fails module resolution when building the torch extension against a current torch_tpu checkout: ERROR: torch_tpu@_ depends on abseil-cpp@20260526.0 with compatibility level 0, but depends on abseil-cpp@20260107.1 with compatibility level 1 which is different Bump the dep and force it with a single_version_override, which selects across the compatibility-level mismatch that a plain bazel_dep cannot (transitive deps such as protobuf still request level-1 releases). --- MODULE.bazel | 13 ++++++++++++- 1 file changed, 12 insertions(+), 1 deletion(-) diff --git a/MODULE.bazel b/MODULE.bazel index dca8611c..df740306 100644 --- a/MODULE.bazel +++ b/MODULE.bazel @@ -78,7 +78,18 @@ use_repo( "stablehlo", ) -bazel_dep(name = "abseil-cpp", version = "20260107.1", repo_name = "com_google_absl") +bazel_dep(name = "abseil-cpp", version = "20260526.0", repo_name = "com_google_absl") + +# abseil-cpp 20260526.0 (required by torch_tpu) is declared incompatible with +# all previous releases: its module metadata dropped `compatibility_level = 1`, +# and bzlmod refuses to mix compatibility levels. Force all dependencies onto +# this version until an abseil release restores the compatibility level +# (https://github.com/abseil/abseil-cpp/pull/2063 dropped it without +# explanation), after which the plain bazel_dep above suffices. +single_version_override( + module_name = "abseil-cpp", + version = "20260526.0", +) # OSS crypto for global_registry_client.cc SHA256. bazel_dep(name = "boringssl", version = "0.20240913.0")