| commit | 0e6cd5c047b799e5e0687739512fa6eb993b0756 | [log] [tgz] |
|---|---|---|
| author | Bazel Release System <noreply@google.com> | Thu Jun 12 17:13:32 2025 +0000 |
| committer | carmenchui@google.com <carmenchui@google.com> | Thu Jun 12 17:13:32 2025 +0000 |
| tree | c8fefe31213b4f6272fd9ed7de40dd44ca0471e4 | |
| parent | 7b9a33fddb59f67f4d100c7a6df5a911376f00d3 [diff] |
Release 9.0.0-pre.20250608.1 (2025-06-12)
Baseline: 7b9a33fddb59f67f4d100c7a6df5a911376f00d3
Incompatible changes:
- strings in attribute's "provides" parameters are no longer
supported
Important changes:
- java_import.jars attributes can no longer be empty, and
--noincompatible_disallow_java_import_empty_jars is no longer
supported
- The `--incompatible_disable_native_repo_rules` flag is flipped
and graveyarded. The `local_config_platform` builtin module has
been removed.
- The `--experimental_split_xml_postprocessing` flag no longer
exists.
This release contains contributions from many people at Google, as well as Fabian Meumertzheim, James Jenkins, Jim Carroll, Jordan Mele, Ryan Matthews, Xdng Yng.
{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.
Follow our tutorials:
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
