Bump dependency versions, drop compatibility_level (#1815)

Removes `compatibility_level` from the `module` directive in
`MODULE.bazel`. Bumps the following dependency versions:

Bazel modules:
- `bazel_features`: 1.38.0 => 1.42.0
- `bazel_skylib`: 1.8.2 => 1.9.0
- `protobuf`: v33.4 => v33.5
- `rules_cc`: 0.2.14 => 0.2.17
- `rules_go`: 0.59.0 => 0.60.0
- `rules_java`: 9.3.0 => 9.6.1
- `rules_python`: 1.7.0 => 1.8.5

Golang:
- Golang: 1.25.5 => 1.26.0
- `golang.org/x/tools`: v0.40.0 => v0.42.2

Maven artifacts:
- `org.scalameta:scalafmt-core_*`: 3.10.2 => 3.10.7
- `org.scala-sbt:compiler-interface`: 1.11.0 => 1.12.0
- `org.scala-sbt:util-interface`: 1.11.7 => 1.12.4
- `org.google.protobuf:protobuf-java`: 4.33.4 => 4.33.5
- `io.grpc:grpc-*`: 1.77.0 => 1.79.0
- `com.google.api.grpc:proto-google-common-protos`: 2.63.1 => 2.66.0

---

Most of the change is a routine dependency version bump before a new
patch level release. There are two specific changes of note.

First, Bazel 8.6.0 and 9.1.0 effectively make the `compatibility_level`
attribute of the `module` directive a no-op per bazelbuild/bazel#28600.

Second, though `protobuf` v34.0 is out, we only update to v35.5 because
v40.0 drops support for Bazel 7 (in maintenance mode until December
2026):

- https://github.com/protocolbuffers/protobuf/releases/tag/v34.0
- protocolbuffers/protobuf@304c9ba
- https://protobuf.dev/support/migration/#dropped-bazel-7-support
- https://bazel.build/release

I'll confer with the Bazel Rules Author SIG on 2026-03-03 regarding
whether or not we should begin planning to deprecate Bazel 7 support.
Doing so would likely necessitate a major version bump to `rules_scala`
8.0.0. (It would be good to get some other large pending changes in
before then, notably the possible `rules_jvm_external` migration.)

Author: mbland

.scalafmt.conf

@@ -1,4 +1,4 @@
-version = "3.10.2"
+version = "3.10.7"
 runner.dialect = scala213
 align.openParenCallSite = false
 align.openParenDefnSite = false

MODULE.bazel

@@ -7,7 +7,6 @@ module(
     # - https://github.com/bazel-contrib/publish-to-bcr/blob/v1.1.0/src/domain/create-entry.ts#L176-L216
     version = "",
     bazel_compatibility = [">=7.1.0"],
-    compatibility_level = 7,
 )
 
 SCALA_VERSION = "2.12.21"
@@ -34,7 +33,7 @@ SCALA_VERSIONS = SCALA_2_VERSIONS + SCALA_3_VERSIONS
 bazel_dep(name = "bazel_skylib", version = "1.8.0")
 single_version_override(
     module_name = "bazel_skylib",
-    version = "1.8.2",
+    version = "1.9.0",
 )
 
 bazel_dep(name = "platforms", version = "0.0.9")
@@ -46,7 +45,7 @@ single_version_override(
 bazel_dep(name = "rules_java", version = "7.6.0")
 single_version_override(
     module_name = "rules_java",
-    version = "9.3.0",
+    version = "9.6.1",
 )
 
 # TODO: Remove this dep once protobuf 33.4 becomes the minimum supported
@@ -60,7 +59,7 @@ bazel_dep(
 )
 single_version_override(
     module_name = "protobuf",
-    version = "33.4",
+    version = "33.5",
 )
 
 # See //src/java/io/bazel/rulesscala/worker:worker_protocol_java_proto.
@@ -245,7 +244,7 @@ bazel_dep(
 )
 bazel_dep(
     name = "rules_go",
-    version = "0.59.0",
+    version = "0.60.0",
     dev_dependency = True,
     repo_name = "io_bazel_rules_go",  # for com_github_bazelbuild_buildtools
 )
@@ -256,7 +255,7 @@ go_sdk = use_extension(
     "go_sdk",
     dev_dependency = True,
 )
-go_sdk.download(version = "1.25.5")
+go_sdk.download(version = "1.26.0")
 
 go_deps = use_extension(
     "@gazelle//:extensions.bzl",
@@ -275,11 +274,11 @@ go_deps = use_extension(
 # - https://go.dev/ref/mod#checksum-database
 #
 #   go list -m golang.org/x/tools@latest
-#   curl https://sum.golang.org/lookup/golang.org/x/tools@v0.38.0
+#   curl https://sum.golang.org/lookup/golang.org/x/tools@v0.42.0
 go_deps.module(
     path = "golang.org/x/tools",
-    sum = "h1:yLkxfA+Qnul4cs9QA3KnlFu0lVmd8JJfoq+E41uSutA=",
-    version = "v0.40.0",
+    sum = "h1:uNgphsn75Tdz5Ji2q36v/nsFSfR/9BRFvqhGBaJGd5k=",
+    version = "v0.42.0",
 )
 go_deps.module(
     path = "github.com/golang/protobuf",
@@ -292,5 +291,5 @@ use_repo(
     "org_golang_x_tools",
 )
 
-bazel_dep(name = "rules_python", version = "1.7.0", dev_dependency = True)
+bazel_dep(name = "rules_python", version = "1.8.5", dev_dependency = True)
 bazel_dep(name = "rules_shell", version = "0.6.1", dev_dependency = True)

MODULE.bazel.lock

@@ -1547,31 +1547,6 @@ use_repo(
 )
 ```
 
-### Bazel module compatibility levels
-
-`rules_scala` 7.0.0 will set the
-[`compatibility_level`](https://bazel.build/external/module#compatibility_level)
-value for its [`module()`](https://bazel.build/rules/lib/globals/module)
-directive. The `compatibility_level` for `rules_scala` will track major version
-numbers (per [semantic versioning](https://semver.org/)), and this `README` will
-clearly document the reason for the level bump. `compatibility_level` mismatches
-in the module graph will cause module resolution to fail, signaling the presence
-of known breaking changes.
-
-The concept of proper `compatibility_level` usage is still up for discussion in
-bazelbuild/bazel#24302. However, the policy above favors forcing module
-resolution to fail, rather than allowing a later execution step to fail with a
-potentially confusing error message. If a version bump may break builds for any
-known reason, we will explain why up front instead of waiting for users to be
-surprised.
-
-[A comment from #1647 illustrates how 'rules_erlang' fails due to
-'compatibility_level' conflicts][erlang]. The ['rules_erlang' 3.0.0 release
-notes](https://github.com/rabbitmq/rules_erlang/releases/tag/3.0.0) describe the
-breaking changes. This seems like a reasonable model to follow.
-
-[erlang]: https://github.com/bazelbuild/rules_scala/issues/1647#issuecomment-2486777859
-
 ## Contributing
 
 See [CONTRIBUTING.md](CONTRIBUTING.md) for more info.

README.md

@@ -6,13 +6,13 @@ module(
     bazel_compatibility = [">=7.1.0"],
 )
 
-bazel_dep(name = "bazel_skylib", version = "1.8.2")
+bazel_dep(name = "bazel_skylib", version = "1.9.0")
 bazel_dep(name = "platforms", version = "1.0.0")
-bazel_dep(name = "protobuf", version = "33.4")
-bazel_dep(name = "rules_java", version = "9.3.0")
+bazel_dep(name = "protobuf", version = "33.5")
+bazel_dep(name = "rules_java", version = "9.6.1")
 bazel_dep(name = "rules_proto", version = "7.1.0")
 
 # https://github.com/bazelbuild/bazel/pull/25681 removed
 # `bazel_tools/tools/cpp/osx_cc_wrapper.sh.tpl` in the `last_green` Bazel as of
 # 2025-04-08. At least `test_cross_build` breaks without this.
-bazel_dep(name = "rules_cc", version = "0.2.14")
+bazel_dep(name = "rules_cc", version = "0.2.17")