| commit | 3a28e18a2278fc1828d619bb865fb9dfd61f9096 | [log] [tgz] |
|---|---|---|
| author | Bazel Release System <noreply@google.com> | Thu Aug 07 20:33:54 2025 +0000 |
| committer | carmenchui@google.com <carmenchui@google.com> | Thu Aug 07 20:33:54 2025 +0000 |
| tree | 704b11769de64f934080d2acc85ff43a3ca7e850 | |
| parent | 861d613a53e22ef1c806299a11585f97b01f15c8 [diff] |
Release 9.0.0-pre.20250730.2 (2025-08-07)
Baseline: b4216efd8c13c564e92115dae25dd6620423bac1
Cherry picks:
+ bbfb288a7b24bff645c62fa2bf3521d1de293cb1:
Fix
https://github.com/bazelbuild/bazel/commit/9aa7583e97bffb17d2a6f4
8aecefa932e8064daa performance regression.
Important changes:
- Tool paths specified in `cc_toolchain` action configs are now
normalized based on the current execution platform's OS rather
than the host OS. In particular, Windows-style absolute paths are
now treated as absolute paths when building on a Windows executor
from a non-Windows host.
This release contains contributions from many people at Google, as well as Austin Schuh, Benjamin Peterson, Ed Schouten, Fabian Meumertzheim, George Gensure, Mike Lundy, Wade Carpenter.
{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
