Release 10.0.0-pre.20260729.1 (2026-08-04)
Baseline: b66e78bad319b5107a5d1be67343a5705360e87a
New features:
- Added `--experimental_remote_cache_chunking_function` to select
the content-defined chunking function used by
`--experimental_remote_cache_chunking`. Supported values are
`auto` (the default, which negotiates the function from the
server capabilities, preferring FastCDC 2020), `fast_cdc_2020`
and `rep_max_cdc`.
Important changes:
- Fixed `repository_ctx.download_and_extract` failing with an
"Expected a file with a ... suffix" error when
`--downloader_config` blocks all URLs and the archive is served
from the repository cache.
- `--incompatible_modify_execution_info_additive` is now deprecated
and a no-op. When `--modify_execution_info` is specified multiple
times, all values are always applied in order.
This release contains contributions from many people at Google, as well as David Zbarsky, Fabian Meumertzheim, ifutivic, Keith Smiley, Tamir Duberstein.
{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
