| commit | 33653aec67a821dd376f093fce062ae2b652799c | [log] [tgz] |
|---|---|---|
| author | Bazel Release System <noreply@google.com> | Tue Mar 29 20:10:59 2022 +0200 |
| committer | fweikert <fwe@google.com> | Tue Mar 29 20:10:59 2022 +0200 |
| tree | 387786c9a31fdd42195e3e8d02807386a756d855 | |
| parent | 77cd575685f405a2f2a9a6549b20ec439dc4ba5f [diff] |
Release 6.0.0-pre.20220324.1 (2022-03-29)
Baseline: 77cd575685f405a2f2a9a6549b20ec439dc4ba5f
Important changes:
- android_sdk_repository read $ANDROID_SDK_ROOT in addition to
$ANDROID_HOME.
- The default dexer is now d8. dx can be optionally enabled using:
--define=android_dexmerger_tool=dx_dexmerger \
--define=android_incremental_dexing_tool=dx_dexbuilder \
--define=android_standalone_dexing_tool=dx_compat_dx \
--use_workers_with_dexbuilder
This release contains contributions from many people at Google, as well as Andreas Herrmann, arunkumar9t2, Benjamin Lee, Benjamin Peterson, Fabian Meumertzheim, gkgoat1, Jan, Jay Bazuzi, Keith Smiley, Nick Korostelev, Oscar Bonilla, Yannic Bonenberger.
{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
