depending on @bazel_tools//src/main/protobuf:deps_java_proto fails in nightly 9.0.0-pre.20250714.1

[nickbreen]

Description of the bug:

Between 9.0.0-pre.20250710.1 and 9.0.0-pre.20250714.1 depending on @bazel_tools//src/main/protobuf:deps_java_proto has started failing with:

ERROR: /home/nick/src/unused-deps/BUILD.bazel:20:12: error loading package '@@bazel_tools//src/main/protobuf': Unable to find package for @@[unknown repo 'com_github_grpc_grpc' requested from @@bazel_tools]//bazel:cc_grpc_library.bzl: The repository '@@[unknown repo 'com_github_grpc_grpc' requested from @@bazel_tools]' could not be resolved: No repository visible as '@com_github_grpc_grpc' from repository '@@bazel_tools'. and referenced by '//:unused-deps'

This is reproduced in https://github.com/nickbreen/rules_unused_deps/actions/runs/16381662043/job/46294255914

Which category does this issue belong to?

Java Rules

What's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.

This is reproduced in https://github.com/nickbreen/rules_unused_deps/actions/runs/16381662043/job/46294255914

Which operating system are you running Bazel on?

Ubuntu Noble
default Ubuntu github action runner

What is the output of bazel info release?

release 9.0.0-pre.20250714.1

If bazel info release returns development version or (@non-git), tell us how you built Bazel.

N/A

What's the output of git remote get-url origin; git rev-parse HEAD ?

N/A

If this is a regression, please try to identify the Bazel commit where the bug was introduced with bazelisk --bisect.

bazelisk --bisect=9.0.0-pre.20250710.1..9.0.0-pre.20250714.1 test ...

first bad commit is https://github.com/bazelbuild/bazel/commit/e6979d3f878ddd663f15a10b09407ecbb9380fee

e6979d3

Have you found anything relevant by searching the web?

No.

Any other information, logs, or outputs that you want to share?

No

[nickbreen]

Minimum reproduction.

#MODULE.bazel
bazel_dep(name = "rules_java", version = "8.13.0")

#BUILD.bazel
load("@rules_java//java:defs.bzl", "java_library")
java_library(
    name = "foo",
    runtime_deps = [
        "@bazel_tools//src/main/protobuf:deps_java_proto",
    ],
)

USE_BAZEL_VERSION=rolling bazelisk fetch ...

[bc-lee]

My local patch resolved the issue. While I’m not an expert in Bazel internals, this change appears to make it explicit that @@bazel_tools depends on the @grpc-java and @com_github_grpc_grpc repositories — dependencies that were previously assumed but not declared:

diff --git a/src/MODULE.tools b/src/MODULE.tools
index f23fc1e3fb..0ec34bd2df 100644
--- a/src/MODULE.tools
+++ b/src/MODULE.tools
@@ -10,6 +10,8 @@ bazel_dep(name = "buildozer", version = "8.2.0.bcr.1")
 bazel_dep(name = "platforms", version = "0.0.11")
 bazel_dep(name = "zlib", version = "1.3.1.bcr.5")
 bazel_dep(name = "rules_proto", version = "7.0.2")
+bazel_dep(name = "grpc", version = "1.73.1", repo_name = "com_github_grpc_grpc")
+bazel_dep(name = "grpc-java", version = "1.71.0")

 # Enforce a minimal required version
 bazel_dep(name = "bazel_features", version = "1.30.0", repo_name = None)

[fmeum]

@meteorcloudy