Release 10.0.0-pre.20260630.1 (2026-07-17)

Baseline: 9eb1ca2fcd0aea034c37dcdcacbde3d86ff1b26f

Cherry picks:

   + 2ed91fa145434a6f82f29071a27f6de9e785e73b:
     Roll-forward: Upgrade to rules_cc 0.2.18 in MODULE.tools
   + e0ce90e80f60ad3d7a479af2a55477f44fd2af9e:
     Fix distribution archive generation

New features:

  - Windows launcher stubs now embed an `asInvoker` UAC manifest,
    preventing "The requested operation requires elevation. (error:
    740)" for targets whose name matches the installer-detection
    heuristic.

Important changes:

  - The remote repo contents cache now correctly materializes chains
    of symlinks as action inputs, but no longer supports symlinks
    into the main repository.
  - Fixed Bazel being unable to run a Windows executable whose path
    is too long to shorten under `MAX_PATH`, e.g. when 8dot3 short
    names are disabled (microsoft/Windows-Containers#507).
  - Fixed spurious "No such file" errors with the remote repo
    contents cache when a repo contains a symlink to a `.bzl` file.
  - Source directories in external repositories are temporarily
    allowed to cross package boundaries. This will be disallowed in
    the future, gated by the new
    `--incompatible_check_external_repo_source_dir_package_boundary`
    flag.
  - Adds `bazel dump --skyframe=keys` to report only the keys
    available in SkyFrame. Always use with `--skykey_filter` to limit
    the number of keys reported.
  - Fixed a crash with `--experimental_remote_repo_contents_cache`
    when running without a remote or disk cache.

This release contains contributions from many people at Google, as well as adilburaksen, Blaine Freestone, c2qd, Chedrian07, cjk, David Zbarsky, Fabian Meumertzheim, Jacob Nowjack, jcater, Markus Hofbauer, Rgis Desgroppes, Son Luong Ngoc, vadim, zhaixiaojuan.
1 file changed
tree: cca815dc2e9f14f233120dcb2335f32c26cc9949
  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
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