fix: add rules_proto and explicit load statements for proto_library / cc_proto_library#13
Merged
Merged
Conversation
paulorsousa
approved these changes
May 26, 2026
2 tasks
paulorsousa
approved these changes
May 27, 2026
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
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.
Problem
CI fails on both
build-and-testandtest-deb-buildjobs with:Root cause
Bazel 9.1.0 (used by CI) with Bzlmod no longer auto-loads
proto_libraryandcc_proto_libraryas built-in rules. These symbols must now be explicitly imported viaload()statements, andrules_protomust be declared as an explicit dependency inMODULE.bazel.Fix
MODULE.bazel— Addbazel_dep(name = "rules_proto", version = "7.1.0").src/BUILD— Add at the top:src/quipper/BUILD— Same two load statements at the top.rules_proto7.1.0 is the current stable release in the Bazel Central Registry and is compatible with Bazel 9.x and protobuf 31.x+.