-
Notifications
You must be signed in to change notification settings - Fork 45
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
Flag --incompatible_disable_starlark_host_transitions will break stardoc in Bazel 7.0 #145
Comments
Hi Team, Gentle ping , Can you share any significant update on this issue. Thanks! |
We are not using host transitions in Stardoc itself - but it's used by many of our deps (skylib, rules_license, rules_jvm_external, rules_cc). We should check whether those projects have releases which work with --incompatible_disable_starlark_host_transitions (for skylib e.g. we need to update to 1.4.1). |
We're blocked by Bazel itself using host transitions in third_party/grpc/build_defs.bzl :)
|
Removes a blocker for buildimg Bazel itself with --incompatible_disable_starlark_host_transition - and unblocks bazelbuild/stardoc#145
Steps to fix:
|
Removes a blocker for buildimg Bazel itself with --incompatible_disable_starlark_host_transition - and unblocks bazelbuild/stardoc#145 Partial commit for third_party/*, see #19192. Signed-off-by: Pavan Singh <[email protected]>
…t_transitions (#179) And to make sure we stay unbroken, add the flag to our ci config - which on Windows requires setting `BAZELISK_SHUTDOWN=1` to work around bazelbuild/continuous-integration#1012 Fixes #145
Incompatible flag
--incompatible_disable_starlark_host_transitions
will be enabled by default in the next major release (Bazel 7.0), thus breaking stardoc. Please migrate to fix this and unblock the flip of this flag.The flag is documented here: bazelbuild/bazel#17032.
Please check the following CI builds for build and test results:
Never heard of incompatible flags before? We have documentation that explains everything.
If you have any questions, please file an issue in https://github.com/bazelbuild/continuous-integration.
The text was updated successfully, but these errors were encountered: