Upgrade to rules_proto_grpc 5+, bazel 8.0 and migrate to use bzlmod, and grpc 1.76.0 #286
Conversation
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
karenyrx
changed the title
added 2 commits
November 5, 2025 22:28
…and grpc 1.76.0 Signed-off-by: karenx <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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
Fix the 19 Java security vulnerabilities in
rules_proto_grpc(netty, okio, google-auth, etc), by upgrading rules_proto_grpc to 5.x.x +. However this version is only compatible with bazel 8+, which only supports BzlMod (MODULE.bazel, MODULE.bazel.lock) rather than WORKSPACE files, so many bazel changes arose as a result.Verification it worked: 19/21 vulnerabilities fixed:
The renaming 2 are related to Typescript deps, which is the proto tooling, not the bazel files which generate the proto generated code, so those will be fixed separately
Issues Resolved
List any issues this PR will resolve, e.g. Closes [...].
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.