Release 10.0.0-pre.20260902.1 (2026-09-10)

Baseline: e2e4c35d7400a1f3cdf3e337bb53e4fa0eafd001

Important changes:

  - Starlark `fail()` calls now format error messages with `Error: `
    instead of `Error in fail: `.
    Resolves https://github.com/bazelbuild/bazel/issues/21523.
  - Aquery now supports the `config(expr, word)` function.
  - Fixed unnecessary remote-cache hits in incremental BwoB builds
    after a previous invocation used a broader remote output download
    policy.
  - Fix an issue on Windows where empty environment variables (e.g.
    `--action_env=VAR=`) caused test execution failures in the test
    wrapper.
  - `--experimental_override_platform_cpu_name` renamed to
    `--override_platform_cpu_name`
  - The macOS sandbox now allows actions to bind sockets when network
    access is blocked, matching the behavior of the Linux sandbox.
    Note that macOS cannot restrict inbound connections by peer, so
    an action that listens on a non-loopback address is reachable
    from other hosts on the network; outbound traffic remains
    restricted to loopback.
  - Clean up unused stashed sandbox directories when shutting down
    the Bazel server.
  - Downloader rewrites to endpoints that refuse connections no
    longer repeat the connector's full retry sequence.
  - Fix `grep: invalid option -- P` errors on macOS when running
    release and documentation scripts.
  - Remote execution, remote caching, and auth flags can now be reset
    to their default unset state on the command line by passing an
    empty value (e.g., `--remote_cache=`, `--remote_executor=`,
    `--google_credentials=`).

This release contains contributions from many people at Google, as well as Alex Eagle, Angus Lees, Armando Montanez, Fabian Meumertzheim, Fabian Meumertzheim, Henner Zeller, jjj-n, Jonathan Perry, justinswe, Keith Smiley, Kip Hamiltons, Salma Samy, Samuel Bronson, Tyler Breisacher, zozo123.
1 file changed
tree: e9ce82542e3f92f2057232db0674ef63cfbe227a
  1. .bazelci/
  2. .devcontainer/
  3. .gemini/
  4. .github/
  5. docs/
  6. examples/
  7. scripts/
  8. site/
  9. src/
  10. third_party/
  11. tools/
  12. .bazelrc
  13. .bazelversion
  14. .gitattributes
  15. .gitignore
  16. AGENTS.md
  17. AUTHORS
  18. bazel_downloader.cfg
  19. BUILD
  20. CHANGELOG.md
  21. CODE_OF_CONDUCT.md
  22. CODEOWNERS
  23. combine_distfiles.py
  24. combine_distfiles_to_tar.sh
  25. compile.sh
  26. CONTRIBUTING.md
  27. CONTRIBUTORS
  28. distdir.bzl
  29. extensions.bzl
  30. LICENSE
  31. maven_install.json
  32. MODULE.bazel
  33. MODULE.bazel.lock
  34. oneversion_allowlist.csv
  35. oneversion_allowlist_for_tests.csv
  36. pyproject.toml
  37. README.md
  38. repositories.bzl
  39. requirements.txt
  40. SECURITY.md
  41. verify_module_bazel_lock.sh
README.md

Bazel

{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.

Getting Started

Documentation

Reporting a Vulnerability

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.

Contributing to Bazel

See CONTRIBUTING.md

Build status