Link to relevant issue and/or commit:
java_tools release request: bazelbuild/java_tools#101.
Upstream Error Prone bump: bazelbuild/bazel#29805 (Error Prone 2.50.0 in bazel MODULE.bazel, commit 316c22bfda, 2026-06-18).
Related (same java_tools/Error Prone area, but orthogonal): #369 — the remotejdk_21 JDK-8341779 backport gap, fixed by #370; that is a JDK pin bump, not an Error Prone version bump.
Other details:
Does this need to be updated in Bazel?
Eventually yes, via the normal rules_java roll into Bazel, so the newer Error Prone reaches Bazel's own build; not blocking.
Does this need to be cherry-picked into a Bazel release?
No.
Any constraints to note?
Depends on java_tools v20.0 being released first (bazelbuild/java_tools#101).
java/repositories.bzl currently pins java_tools v19.0, which bundles Error Prone 2.46.0; every rules_java release from 9.5.0 through 9.7.0 therefore ships 2.46.0 to downstream projects even though bazel master moved to 2.50.0 in #29805.
Once v20.0 is released, bump the _JAVA_TOOLS block in java/repositories.bzl and cut a rules_java release.
#370 should also be merged with or before this bump. Error Prone 2.50 still has the NullArgumentForNonNullParameter check, so shipping it while remotejdk_21 remains on the un-backported Zulu 21.0.9 would keep the #369 false positives firing under the Java 21 toolchain (the JDK, not the Error Prone version, is what cannot read the annotation).
cc @bazelbuild/triage
Link to relevant issue and/or commit:
java_tools release request: bazelbuild/java_tools#101.
Upstream Error Prone bump: bazelbuild/bazel#29805 (Error Prone 2.50.0 in bazel MODULE.bazel, commit 316c22bfda, 2026-06-18).
Related (same java_tools/Error Prone area, but orthogonal): #369 — the remotejdk_21 JDK-8341779 backport gap, fixed by #370; that is a JDK pin bump, not an Error Prone version bump.
Other details:
Eventually yes, via the normal rules_java roll into Bazel, so the newer Error Prone reaches Bazel's own build; not blocking.
No.
Depends on java_tools v20.0 being released first (bazelbuild/java_tools#101).
java/repositories.bzlcurrently pins java_tools v19.0, which bundles Error Prone 2.46.0; every rules_java release from 9.5.0 through 9.7.0 therefore ships 2.46.0 to downstream projects even though bazel master moved to 2.50.0 in #29805.Once v20.0 is released, bump the
_JAVA_TOOLSblock injava/repositories.bzland cut a rules_java release.#370 should also be merged with or before this bump. Error Prone 2.50 still has the NullArgumentForNonNullParameter check, so shipping it while remotejdk_21 remains on the un-backported Zulu 21.0.9 would keep the #369 false positives firing under the Java 21 toolchain (the JDK, not the Error Prone version, is what cannot read the annotation).
cc @bazelbuild/triage