Release 10.0.0-pre.20260614.1 (2026-06-22)
Baseline: e05fcb1658bce403337a3e73a0ca184c45128ad6
Important changes:
- Fixed repo content caching for non-gRPC cache backends.
- CCStarlarkInternal exposes hash functions currently used by
rules_cc Java rules to starlark
- The new `--expand_param_files` flag expands param files into
their contents in `--subcommands` and `--verbose_failures` output.
- Fixed a performance regression in Bazel 9 that causes
`RepoMappingManifest` actions to consume a lot of CPU time.
- Improved BES upload failure message with failed invocation's ID.
- Any existing action relying on the legacy hardcoded list in Bazel
code being populated will now need to opt-into output mapping by
modifying their execution requirements.
This release contains contributions from many people at Google, as well as Benjamin Peterson, Bryce Lampe, Fabian Meumertzheim, honnix, Keith Smiley, peakschris.
{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
