| commit | 847e9540b97037d39e5d27354ebafcd8236fee35 | [log] [tgz] |
|---|---|---|
| author | Bazel Release System <noreply@google.com> | Fri Nov 11 19:00:59 2022 +0100 |
| committer | fweikert <fwe@google.com> | Fri Nov 11 19:00:59 2022 +0100 |
| tree | 79f44116b3766b590233fdb38493bc3e963ae45d | |
| parent | 19b8d24531fb728701a85ec050361d434600b5d2 [diff] |
Release 7.0.0-pre.20221102.3 (2022-11-11)
Baseline: 19b8d24531fb728701a85ec050361d434600b5d2
Incompatible changes:
- This has the side effect of changing the message on unsuccessful
builds from
```
FAILED: Build did NOT complete successfully (0 packages loaded)
```
to
```
ERROR: Build did NOT complete successfully
```
- Bazel no longer increases the delay between progress updates when
there is no cursor control.
- This has the side effect of changing the message on unsuccessful
builds from
```
FAILED: Build did NOT complete successfully (0 packages loaded)
```
to
```
ERROR: Build did NOT complete successfully
```
This release contains contributions from many people at Google, as well as Ed Schouten, Fabian Meumertzheim, Keith Smiley, Krzysztof Naglik, Patrick Balestra, Tom Cnops, Xdng Yng, Xiangquan Xiao.
{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
