Release 10.0.0-pre.20260801.1 (2026-08-10)
Baseline: 14498c82d1af1ee127ac2140f0bfdf0f62d36c60
Cherry picks:
+ 909985a3b9a1f71106e7cba31eb862078e5bdebe:
Automated rollback of commit
2558ffede4c29cc41c7080eadd3118cb12509517.
Incompatible changes:
- The Windows shell launcher now again prepends rather than appends
the directory containing the shell binary, restoring the behavior
of Bazel 8.x. This is technically an incompatible change, but
deemed necessary due to the unexpected and widespread
implications of the change in 9.0.0. See
https://github.com/bazelbuild/bazel/issues/29637 for more context.
New features:
- The `BAZEL_LLVM_PROFILE_FILE` environment variable can now
be used to customize the LLVM profile filename pattern for C++
coverage
collection (e.g. `--test_env=BAZEL_LLVM_PROFILE_FILE=%p.profraw`).
Defaults to `%h-%p-%m.profraw` when unset.
Important changes:
- --experimental_split_coverage_processing and
--experimental_fetch_all_coverage_outputs default to true.
- Retry 408 and 429 status codes with HTTP remote caching.
- Fixed a bug that could cause `ignore_directories()` to not ignore
directories.
This release contains contributions from many people at Google, as well as Akshay Ubale, Benjamin Peterson, Bryce Lampe, Chi Wang, Fabian Meumertzheim, Fabian Meumertzheim, Fabian Meumertzheim, George Gensure, Javier Maestro, Keith Smiley, Matthew Steffen, PikachuHy, Son Luong Ngoc, Tamir Duberstein, Tyler Breisacher, Xdng Yng, Yossi Eliaz, zozo123.
{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
