| commit | eb234b1d9ccd250df8837c8ec225db944ce661c7 | [log] [tgz] |
|---|---|---|
| author | Damian Banki <ddaniel.banki@gmail.com> | Fri Feb 06 11:41:11 2026 -0800 |
| committer | Copybara-Service <copybara-worker@google.com> | Fri Feb 06 11:42:26 2026 -0800 |
| tree | 050dd65f9885e7fc20804be059300c70870f287c | |
| parent | ed98d31d352a41595d9f4561fae501bd67a43826 [diff] |
Add deprecation warning to --build_python_zip. (https://github.com/bazelbuild/bazel/pull/28527) There was an [issue](https://github.com/bazelbuild/bazel/issues/28348) surfaced where the native semantic `--nobuild_python_zip` had become a no-op due to the graveyarding/starlarkification of the option. The starlark flag version must use the `=` operator for assignment and can no longer work with the prefixed `no` option. This information was not surfaced in a great way causing confusion. Closes #28527. PiperOrigin-RevId: 866548743 Change-Id: Iff42d8f98767c9136757dfe318ac2ee054286509
{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.
Follow our tutorials:
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
