Migrate to MODULE.bazel to support Bazel 7 #6
Conversation
This file contains 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.
Migrate to MODULE.bazel to support Bazel 7
Bazel 7 just came out and it is backward incompatible with existing WORKSPACE dependencies. This particular repo is not immediately affected, but up-stream repos are, such as x-edr-eigenmath, and mobility repos. The root problem is that there is a race between MODULE.bazel migration in Bazel and migrations away from native rules in rules_cc and rules_proto, which means that in the current state, things are very broken when using protobuf unless we migrate immediately to MODULE.bazel.