| commit | dd46a31d7a1d69786061e4c00d3cbc896508835b | [log] [tgz] |
|---|---|---|
| author | Bazel Release System <noreply@google.com> | Fri May 03 20:13:01 2024 +0200 |
| committer | Florian Weikert <fwe@google.com> | Fri May 03 20:13:01 2024 +0200 |
| tree | 10c7ed36dd3dbc5f0e573a9b4e0089d2270c937d | |
| parent | fa03d7e1eb7affeecfb0b01d4c4d797988e37653 [diff] |
Release 8.0.0-pre.20240422.4 (2024-05-03)
Baseline: d37762b494a4e122d46a5a71e3a8cc77fa15aa25
Cherry picks:
+ f14c99e83b339a3f926285f62807a03dea3b0479:
Automated rollback of commit
a091d90cded797ce8f6206b56ffd6f89e27e2c76.
+ eb70fc222755a4249759729587600de828029e71:
Keep aspects that relate to uncleared configured targets from
being cleared.
+ e22a6938b411b3ba29a8bfcf2a18208bf28d04b0:
Automated rollback of commit
76a214932da4a9dcf73d3cfe9313e0172d20e630.
Incompatible changes:
- On Windows, the default msys64 root is changed to `C:/msys64`
instead of `C:/tools/msys64`.
Important changes:
- `distribs()` at the package level is no longer legal syntax. It
may still be set on individual targets, even though it is a no-op.
This release contains contributions from many people at Google, as well as dependabot[bot], Fabian Meumertzheim, Son Luong Ngoc, Spencer Putt, 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
