commit | 46fb76e9d2dc1a2c4a62f75ca3994047d1d9235f | [log] [tgz] |
---|---|---|
author | Bazel Release System <noreply@google.com> | Mon Jan 13 15:26:52 2025 +0000 |
committer | keertk <keerthanakumar@google.com> | Mon Jan 13 15:26:52 2025 +0000 |
tree | 056213faf03be8f41d9c8060c9ab9f4ee7bf7e0e | |
parent | fa48bc66e7118ca251c73bdad2c94039f51b5301 [diff] |
Release 9.0.0-pre.20250106.2 (2025-01-13) Baseline: fa48bc66e7118ca251c73bdad2c94039f51b5301 Important changes: - Baseline coverage files are no longer ignored. - select() on `cpu`, `host_cpu`, or `crosstool_top now emits a "deprecated flag" warning - `--max_idle_secs` now takes system sleep time into account when deciding when to shutdown the blaze server. - Flip --experimental_enable_starlark_set and enable the Starlark set data type by default. This release contains contributions from many people at Google, as well as Alessandro Patti, Boleyn Su, Eric Riff, Fabian Meumertzheim, Keith Smiley, Kiron, Pareesh Madan, Steve Barrau, Torgil Svensson.
{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