Bring Bazel builds into compliance with upcoming breaking changes #15363
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
![copybara-service[bot]](https://avatars.githubusercontent.com/in/44061?s=60&v=4){kind=small}
This change makes our Bazel build compatible with all the migration-ready `--incompatible` flags listed [here](https://github.com/bazelbuild/bazel/releases/tag/7.0.0) for Bazel 7.0, with a couple exceptions listed below. This was mostly just a matter of updating some of our dependencies to more recent versions. The two flags we cannot support yet are these: - `--incompatible_disallow_struct_provider_syntax`: Bazel itself appears not to support this one yet, see [here](bazelbuild/bazel#19467). - `--incompatible_stop_exporting_language_modules`: waiting on support in `rules_jvm_external`, see [here](bazel-contrib/rules_jvm_external#1027). I also deleted the broken `//:protobuf_nowkt` alias target, which was an oversight on my part from a previous change. PiperOrigin-RevId: 597076542
copybara-service
bot
force-pushed
the
test_597076542
branch
from
7a6667b to
c1cbc40
Compare
|
Auto-closing Copybara pull request |
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.
Bring Bazel builds into compliance with upcoming breaking changes
This change makes our Bazel build compatible with all the migration-ready
--incompatibleflags listedhere for Bazel 7.0,
with a couple exceptions listed below. This was mostly just a matter of
updating some of our dependencies to more recent versions.
The two flags we cannot support yet are these:
--incompatible_disallow_struct_provider_syntax: Bazel itself appears notto support this one yet, see
here.
--incompatible_stop_exporting_language_modules: waiting on support inrules_jvm_external, seehere.
I also deleted the broken
//:protobuf_nowktalias target, which was anoversight on my part from a previous change.