-
Notifications
You must be signed in to change notification settings - Fork 4.4k
[7.2.0] Make Bazel changes for oneversion support
#22635
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
This is a partial cherry-pick of 417c6b8 which excludes the changes to `oneversion` itself, which is built and released for Bazel 7 as part of java_tools: * Avoid passing --whitelist to one_version if no allowlist is configured in the toolchain as it isn't supported by the Bazel version of oneversion yet. * Document the one_version flags. * Clean up tests not updated after recent rules_java releases.
oneversion supportoneversion support
|
@fmeum, how urgent is this change? And how would you characterize the risk for breakage if we include it? I'm asking because even though we're doing an rc3, I'd very much like to avoid any further delays on the release. Ideally we shouldn't be cherry-picking anything that's not an rc1/rc2 regression at this point. |
|
I fully understand your concerns, happy to provide the context for you to make a call:
|
|
Well, turned out we need 193b114 to make sure Bazel still builds in our trusted environment where there is an older macOS version. |
|
Oh, just realized this is a partial cherry-pick, which doesn't touch abseil-cpp version, then we don't need the fix on the main branch. |
|
Sounds good! @cushon could you approve the PR please? |
This is a partial cherry-pick of 417c6b8 which excludes the changes to
oneversionitself, which is built and released for Bazel 7 as part of java_tools:Fixes #22576