Revert "Upgrade to Bazel 7.7.0, rules_python 1.0.0, protobuf v29"#87
Merged
Conversation
This reverts commit 4834182.
onelxj
approved these changes
Feb 18, 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
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.
Reverts #86 until we can get the
monorepo into a state where it can build using this change.We've seen in https://github.com/reboot-dev/pyprotoc-plugin (where the same move-to-bazel-7 took place) that, when the repo is left in this can't-be-used-in-
mono-state for too long, we end up in an uncomfortable position when needing to land new changes on the repo. Furthermore, our submodule sync bot now runs a failing CI check for every commit that goes intomono, which is a waste of money and carbon.By reverting this change for now we don't lose anything, we can revert the revert when we're ready to accept a Bazel 7 upgrade into
mono.