Bump dependency versions, drop compatibility_level#1815
Merged
mbland merged 1 commit intobazel-contrib:masterfrom Feb 27, 2026
Merged
Bump dependency versions, drop compatibility_level#1815mbland merged 1 commit intobazel-contrib:masterfrom
mbland merged 1 commit intobazel-contrib:masterfrom
Conversation
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.)
WojciechMazur
approved these changes
Feb 27, 2026
mbland
added a commit
to mbland/rules_scala
that referenced
this pull request
Mar 3, 2026
Restores `compatibility_level = 7` to the `module` directive and yanks version 7.2.3 from the Bazel Central Registry. --- Per bazel-contrib#1816, bazel-contrib#1815 removed the `compatibility_level` attribute of the `module` directive too soon. Builds using Bazel <8.6.0 or <9.1.0 with other `rules_scala` 7.x dependencies in the build graph would break once any module introduces `rules_scala` 7.2.3.
mbland
added a commit
that referenced
this pull request
Mar 5, 2026
Restores `compatibility_level = 7` to the `module` directive and yanks version 7.2.3 from the Bazel Central Registry. --- Per #1816, #1815 removed the `compatibility_level` attribute of the `module` directive too soon. Builds using Bazel <8.6.0 or <9.1.0 with other `rules_scala` 7.x dependencies in the build graph would break once any module introduces `rules_scala` 7.2.3.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Removes
compatibility_levelfrom themoduledirective inMODULE.bazel. Bumps the following dependency versions:Bazel modules:
bazel_features: 1.38.0 => 1.42.0bazel_skylib: 1.8.2 => 1.9.0protobuf: v33.4 => v33.5rules_cc: 0.2.14 => 0.2.17rules_go: 0.59.0 => 0.60.0rules_java: 9.3.0 => 9.6.1rules_python: 1.7.0 => 1.8.5Golang:
golang.org/x/tools: v0.40.0 => v0.42.2Maven artifacts:
org.scalameta:scalafmt-core_*: 3.10.2 => 3.10.7org.scala-sbt:compiler-interface: 1.11.0 => 1.12.0org.scala-sbt:util-interface: 1.11.7 => 1.12.4org.google.protobuf:protobuf-java: 4.33.4 => 4.33.5io.grpc:grpc-*: 1.77.0 => 1.79.0com.google.api.grpc:proto-google-common-protos: 2.63.1 => 2.66.0Motivation
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_levelattribute of themoduledirective a no-op per bazelbuild/bazel#28600.Second, though
protobufv34.0 is out, we only update to v35.5 because v40.0 drops support for Bazel 7 (in maintenance mode until December 2026):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_scala8.0.0. (It would be good to get some other large pending changes in before then, notably the possiblerules_jvm_externalmigration.)