From eb8f23387936d23a691075072135fc3f1c09df61 Mon Sep 17 00:00:00 2001 From: Ted Kaplan Date: Thu, 11 Jun 2026 18:55:00 -0700 Subject: [PATCH] Make rules_python, rules_nodejs, rules_foreign_cc dev_dependencies These three bazel_deps exist only to bump transitive dependencies to Bazel 9 compatible versions, which only matters when building bazel-diff as the root module. rules_nodejs and rules_foreign_cc are referenced by no bazel-diff target; rules_python is pulled in transitively (proto codegen) regardless of the explicit edge. Marking them dev_dependency keeps them out of the dependency graph that downstream consumers inherit. --- MODULE.bazel | 12 ++++++++---- 1 file changed, 8 insertions(+), 4 deletions(-) diff --git a/MODULE.bazel b/MODULE.bazel index 2865319..1820d6e 100644 --- a/MODULE.bazel +++ b/MODULE.bazel @@ -25,10 +25,14 @@ single_version_override( bazel_dep(name = "grpc", version = "1.76.0", repo_name = "com_github_grpc_grpc") -# Override transitive dependencies to Bazel 9 compatible versions -bazel_dep(name = "rules_nodejs", version = "6.7.3") -bazel_dep(name = "rules_foreign_cc", version = "0.15.1") -bazel_dep(name = "rules_python", version = "1.8.4") +# Override transitive dependencies to Bazel 9 compatible versions. +# Marked dev_dependency: these are only needed when building bazel-diff itself +# (as the root module). rules_nodejs and rules_foreign_cc are not referenced by +# any bazel-diff target, and rules_python is supplied transitively (proto codegen) +# regardless, so consumers resolve their own versions via MVS. +bazel_dep(name = "rules_nodejs", version = "6.7.3", dev_dependency = True) +bazel_dep(name = "rules_foreign_cc", version = "0.15.1", dev_dependency = True) +bazel_dep(name = "rules_python", version = "1.8.4", dev_dependency = True) maven = use_extension("@rules_jvm_external//:extensions.bzl", "maven") maven.install(