| commit | 0d2bcb8e77b934a8ccb41c744e733238df504c44 | [log] [tgz] |
|---|---|---|
| author | Bazel Release System <noreply@google.com> | Fri May 23 19:31:35 2025 +0000 |
| committer | carmenchui@google.com <carmenchui@google.com> | Fri May 23 19:31:35 2025 +0000 |
| tree | 6a3c41c75c9dc3bf990ced4a0d74e93d60165efa | |
| parent | 9b8093bb4db3d6567e0f29eaa98fe16cd2e4a154 [diff] |
Release 9.0.0-pre.20250516.1 (2025-05-23)
Baseline: 9b8093bb4db3d6567e0f29eaa98fe16cd2e4a154
Incompatible changes:
- Starlark computation step limits are now enforced for symbolic
macros.
Important changes:
- java_import.jars attributes can no longer be empty, and
--noincompatible_disallow_java_import_empty_jars is no longer
supported
- Added `--verbose_visibility_errors` for printing more information
when a visibility violation occurs.
- Added a new flag `--repo_contents_cache` (defaults to the
`contents` directory under the `--repository_cache`) where Bazel
stores fetched contents of repos that can be safely cached across
workspaces. A repo rule can indicate cacheability by returning
`repository_ctx.repo_metadata(reproducible=True)` from its
implementation function.
This release contains contributions from many people at Google, as well as Adin Cebic, Benjamin Peterson, Bo Zhang, Chris Sauer, dependabot[bot], Dmitry Ivankov, Fabian Meumertzheim, George Gensure, Grzegorz Lukasik, jacqueline.lee, Jonathan Schear, Thi Don, 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
