| commit | 6f6e308b728c1a7933de81bd365f8ec9a988f92b | [log] [tgz] |
|---|---|---|
| author | Bazel Release System <noreply@google.com> | Tue Apr 26 21:19:33 2022 +0200 |
| committer | fweikert <fwe@google.com> | Tue Apr 26 21:19:33 2022 +0200 |
| tree | e45166027f78943d5e4ee3f6b22a3a39cfcc9d5b | |
| parent | 46aa45bd5ec86b77ac23f4a25f2c2887013831bc [diff] |
Release 6.0.0-pre.20220414.2 (2022-04-26)
Baseline: 6872fd230b7fe4a15fa900d16f6f9ddd5726cdc3
Cherry picks:
+ a603c2382ffcc49f344eee73dfcd65aa2332f64f:
Automated rollback of commit
b93f828133e74cb3589ba7ffcfe74d2fe72430cd.
+ 6142eac9153b539661c43dada5e11b552a6f58f6:
Automated rollback of commit
314b0900cec69a9d017ab84e94ee1cc0b6782470.
Important changes:
- Bazel uses the D8 jar from Maven instead of the SDK.
- Make ijar / java_import preserve classes with `@kotlin.Metadata`
annotations
- Bazel uses the D8 jar from Maven instead of the SDK.
- android_sdk_repository read $ANDROID_SDK_ROOT in addition to
$ANDROID_HOME.
This release contains contributions from many people at Google, as well as Alex Torok, gkorlam, hvadehra, Vasilios Pantazopoulos, Yannic.
{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
