-
Notifications
You must be signed in to change notification settings - Fork 522
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 rules_nodejs in Bazel 7.0 #3613
Comments
This issue has been automatically marked as stale because it has not had any activity for 6 months. It will be closed if no further activity occurs in 30 days. Collaborators can add a "cleanup" or "need: discussion" label to keep it open indefinitely. Thanks for your contributions to rules_nodejs! |
Hi Team, Gentle ping , Can you share any significant update on this issue. Thanks! |
This issue has been automatically marked as stale because it has had no recent activity. It will be closed if no further activity occurs in 30 days. Note as of rules_nodejs v6 the rules_nodejs repository contains only the core nodejs toolchain and |
This is not yet fixed. Please update! |
I tried turning this flag on, but it looks like the latest stardoc release depends on a broken rules_license:
|
This issue has been automatically marked as stale because it has had no recent activity. It will be closed if no further activity occurs in 30 days. Note as of rules_nodejs v6 the rules_nodejs repository contains only the core nodejs toolchain and |
This issue was automatically closed because it went 30 days without any activity since it was labeled "Can Close?" |
Incompatible flag
--incompatible_disable_starlark_host_transitions
will be enabled by default in the next major release (Bazel 7.0), thus breaking rules_nodejs. 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: