Restrict private builtins cc_common APIs to rules_cc. The builtins `cc_common` wrappers for private APIs (`check_experimental_cc_shared_library`, `incompatible_disable_objc_library_transition`, `add_go_exec_groups_to_binary_rules`, `get_tool_requirement_for_action`, `implementation_deps_allowed_by_allowlist`, `register_swig_action`) were gated by `PRIVATE_STARLARKIFICATION_ALLOWLIST`, a broad list covering Android, Apple, Go, Java, protobuf, Rust, Python, and other rule sets. In practice the only remaining callers are in rules_cc, which reaches the native `cc_common` through rules_impl/native_cc_common.bzl and enforces its own allowlist in cc/private/visibility.bzl. Remove `PRIVATE_STARLARKIFICATION_ALLOWLIST` from cc_helper_internal.bzl and gate these APIs in both the Blaze (cc_common.bzl) and Bazel (cc_common_bazel.bzl) flavors with a rules_cc-only list, shared with `internal_DO_NOT_USE`. PiperOrigin-RevId: 1006104177 Change-Id: I1761503297722b2a51d87a2b6cd526f90b6a1dad
{Fast, Correct} - Choose two
Build and test software of any size, quickly and reliably.
Speed up your builds and tests: Bazel rebuilds only what is necessary. With advanced local and distributed caching, optimized dependency analysis and parallel execution, you get fast and incremental builds.
One tool, multiple languages: Build and test Java, C++, Android, iOS, Go, and a wide variety of other language platforms. Bazel runs on Windows, macOS, and Linux.
Scalable: Bazel helps you scale your organization, codebase, and continuous integration solution. It handles codebases of any size, in multiple repositories or a huge monorepo.
Extensible to your needs: Easily add support for new languages and platforms with Bazel's familiar extension language. Share and re-use language rules written by the growing Bazel community.
To report a security issue, please email security@bazel.build with a description of the issue, the steps you took to create the issue, affected versions, and, if known, mitigations for the issue. Our vulnerability management team will respond within 3 working days of your email. If the issue is confirmed as a vulnerability, we will open a Security Advisory. This project follows a 90 day disclosure timeline.
See CONTRIBUTING.md
