| commit | 82650b19d2fe4ee8bfaba20b64f0db489b11287c | [log] [tgz] |
|---|---|---|
| author | Bazel Release System <noreply@google.com> | Fri Jul 11 23:49:07 2025 +0000 |
| committer | carmenchui@google.com <carmenchui@google.com> | Fri Jul 11 23:49:07 2025 +0000 |
| tree | f4fb518110e9b8fc41732e000908e0d88d27a14f | |
| parent | e08faa5de8095fe27223b6af84b41fd135aa9b4a [diff] |
Release 9.0.0-pre.20250706.3 (2025-07-11)
Baseline: 07bd9661b56710aac7670738e81338715946785e
Important changes:
- Branches will always be merged as best as possible based on
branch and
block numbers during coverage report generation.
- `--experimental_worker_for_repo_fetching` is removed.
- Modules backed by `http_archive` or `git_repository` no longer
require a MODULE.bazel file to be contained in the source archive.
This release contains contributions from many people at Google, as well as Adrian Vogelsgesang, Benjamin Peterson, dependabot[bot], Fabian Meumertzheim, Javier Maestro, Jordan Mele, Keith Smiley, 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
