| commit | 712a319aef4316ee69bbce2e15874b569c9bd2e6 | [log] [tgz] |
|---|---|---|
| author | Bazel Release System <noreply@google.com> | Mon Oct 06 15:23:09 2025 +0000 |
| committer | Carmen Chui <carmenchui@google.com> | Mon Oct 06 15:23:09 2025 +0000 |
| tree | a5a5939940193263e33b61d1c6e73200e7ada2af | |
| parent | 5ac5fd7e961a704675a044794c66299c906de843 [diff] |
Release 9.0.0-pre.20250921.2 (2025-10-06)
Baseline: 906b91b824092e1e5ec156afb5794e4a8a5119df
Cherry picks:
+ 9ec3d27016e11d8c32193f5904a7c2b5d84887e4:
Do not use starlark flag aliases in exec transitions
+ 5639134ce52acad91dc235aaf7df3e73b1cf0da3:
Fix load statements for Java
Important changes:
- `--incompatible_use_python_toolchains=false` no longer works.
Python rules can no longer set runtimes with `--python_top`. See
https://rules-python.readthedocs.io/en/latest/toolchains.html for
toolchain & runtime configuration guidance.
This release contains contributions from many people at Google, as well as Benjamin Peterson, Carmen Chui, Fabian Meumertzheim, Keith Smiley, Peter Lukacs, Ricard Sol, Wade Carpenter.
{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
