| commit | ef8f4469398e9076e95ce84b21acb8a28b86787d | [log] [tgz] |
|---|---|---|
| author | Bazel Release System <noreply@google.com> | Fri Sep 20 03:00:52 2024 +0200 |
| committer | Florian Weikert <fwe@google.com> | Fri Sep 20 03:00:52 2024 +0200 |
| tree | 9a18de26ddf20c4688752d14a8afe64aaa4a2bcd | |
| parent | ad2ea0736eca30ef1f5ad0b46292cb03e43eec5c [diff] |
Release 8.0.0-pre.20240911.1 (2024-09-20)
Baseline: ad2ea0736eca30ef1f5ad0b46292cb03e43eec5c
Incompatible changes:
- --legacy_important_outputs is flipped to false. See #14353 for
details
Important changes:
- Uploading local action results to a disk or remote cache now
occurs in the background whenever possible, potentially
unblocking the execution of followup actions. Set
`--noremote_cache_async` to revert to the previous behavior.
- Overrides in the root MODULE.bazel file are now ignored with
`--ignore_dev_dependency`. (Overrides in non-root modules are
already ignored.)
- Added support for using a remote cache that evicts blobs and
doesn't have AC integrity check (e.g. HTTP cache).
This release contains contributions from many people at Google, as well as Benjamin Peterson, Fabian Meumertzheim, Jacob Van De Weert, John Millikin.
{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
