Release 9.0.0-pre.20251008.2 (2025-10-17)

Baseline: f7538936d349ccb323724f0fa31554f4c97c6fd8

New features:

  - The new `ctx.configuration.short_id` field provides a short
    identifier for the current configuration that is understood by
    `bazel config`.
  - Module extensions can store a JSON-like Starlark object in
    `module_ctx.extension_metadata(facts = ...)` and retrieve it back
    in future evaluations of the extension via `module_ctx.facts`
    without any invalidation taking place.

Important changes:

  - With the new `--incompatible_eagerly_resolve_select_keys` flag,
    the label string keys of `select` dicts in `.bzl` files are
    resolved relative to the containing file instead of relative to
    the BUILD file that ends up using the `select`. Use
    `native.package_relative_label` if this is not desired.
  - native.existing_rule() and native.existing_rules() now correctly
    handle
    labels pointing to a different repo.
  - Starlark string.split(), string.rsplit() now allow sep and
    maxsplit to be
    provided as keyword arguments.
  - With `--experimental_check_external_repository_files` enabled
    (the default), Bazel will now refetch the respective repositories
    when it encounters external modifications. This is necessary to
    ensure correct incrementality. If you rely on external
    modifications to these repositories, either disable or the flag
    or use a supported mechanism such as `--override_repository`,
    `local_path_override` or `override_repo`.
  - `ctx.actions.symlink` now accepts a `target_type` argument.

This release contains contributions from many people at Google, as well as Alex Eagle, Benjamin Peterson, Bradley Bridges, Christian Scott, Christopher Rydell, David Sanderson, David Zbarsky, dependabot[bot], Fabian Meumertzheim, George Gensure, Grzegorz Lukasik, Jonathan Schear, Jordan Mele, Jordan Mele, Nathan Naze, PikachuHy, Ruoyu Zhong, Son Luong Ngoc, Timothy Gu, Ulrik Falklof.
1 file changed
tree: e71d4f2bdfa447e0d437d48a44e36eafd7b0eb8b
  1. .bazelci/
  2. .github/
  3. examples/
  4. scripts/
  5. site/
  6. src/
  7. third_party/
  8. tools/
  9. .bazelrc
  10. .bazelversion
  11. .gitattributes
  12. .gitignore
  13. AUTHORS
  14. bazel_downloader.cfg
  15. BUILD
  16. CHANGELOG.md
  17. CODE_OF_CONDUCT.md
  18. CODEOWNERS
  19. combine_distfiles.py
  20. combine_distfiles_to_tar.sh
  21. compile.sh
  22. CONTRIBUTING.md
  23. CONTRIBUTORS
  24. distdir.bzl
  25. extensions.bzl
  26. LICENSE
  27. maven_install.json
  28. MODULE.bazel
  29. MODULE.bazel.lock
  30. README.md
  31. repositories.bzl
  32. requirements.txt
  33. SECURITY.md
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