| commit | 18b611a17d72b7c15eaec6f69de22d193437889f | [log] [tgz] |
|---|---|---|
| author | Bazel Release System <noreply@google.com> | Fri Feb 24 21:18:58 2023 +0100 |
| committer | fweikert <fwe@google.com> | Fri Feb 24 21:18:58 2023 +0100 |
| tree | a5026b15e325395d8cbeb3b2734866f3193d3dfb | |
| parent | 472609eced1c7669d62c61f19cf69785206d1306 [diff] |
Release 7.0.0-pre.20230215.2 (2023-02-24)
Baseline: e8a69f5d5acaeb6af760631490ecbf73e8a04eeb
Cherry picks:
+ 4ef636552b86ddea01f36c9346b78016bdad7798:
Check for ctx.configuration.coverage_enabled instead of
ctx.coverage_instrumented() in cc_helper.
Incompatible changes:
- When remote cache evicts blobs, Bazel will exit with code 39.
Important changes:
- Update Android manifest merger to v30.1.3, and also drop support
for legacy (pre-D8) desugaring.
- Adds coverage metric support to android_local_test
- Correctly encode double value positive infinity as "inf" instead
of "+inf" for textprotos.
This release contains contributions from many people at Google, as well as Andreas Herrmann, Benjamin Lee, Daniel Grunwald, Emil Kattainen, Fabian Meumertzheim, hvd, keertk, Keith Smiley, kshyanashree, Kun-Lu.
{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
