| commit | 1f5b0a99eb9787e522256177ee1ef52941e77f0d | [log] [tgz] |
|---|---|---|
| author | Bazel Release System <noreply@google.com> | Fri Oct 31 16:20:00 2025 +0000 |
| committer | Carmen Chui <carmenchui@google.com> | Fri Oct 31 16:20:00 2025 +0000 |
| tree | 486426222410913f209b4e42d7bbe996b12b149d | |
| parent | d4980887951f011448b39b5b973d346ea03aab75 [diff] |
Release 9.0.0-pre.20251025.1 (2025-10-31)
Baseline: d4980887951f011448b39b5b973d346ea03aab75
New features:
- Add support for setting the `.bazelrc` path via a `BAZELRC`
environment variable.
Important changes:
- OSS Bazel permits but ignores type annotations in .bzl files.
Type annotations are experimental, and code that uses them may
fail in future versions of Bazel.
- If a java_import target's srcjar attribute refers to a source
file, the file should exist.
This release contains contributions from many people at Google, as well as Alessandro Patti, Alexander Golovlev, Benjamin Peterson, Fabian Meumertzheim, Keith Smiley, Will Stranton.
{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
