| commit | 49dd8e93cc7215e59242b7e4d775aa4effe2228f | [log] [tgz] |
|---|---|---|
| author | Bazel Release System <noreply@google.com> | Thu Sep 15 17:59:42 2022 +0200 |
| committer | fweikert <fwe@google.com> | Thu Sep 15 17:59:42 2022 +0200 |
| tree | b80e901be4937124f826d098ef51db4aa91680f2 | |
| parent | d3bef49f9182f6bcb6f609530970a7945ce51cbf [diff] |
Release 6.0.0-pre.20220909.2 (2022-09-15)
Baseline: d3bef49f9182f6bcb6f609530970a7945ce51cbf
Incompatible changes:
- analysis_test moved into testing.analysis_test
Important changes:
- selects() no longer produce irrelevant duplicate label checks
- Adds a dexer output cache to CompatDexBuilder to improve build
speed.
- Improved error messages when analyzing inline bzl code
- Improved error messages when analyzing inline bzl code
This release contains contributions from many people at Google, as well as Alessandro Patti, Benjamin Peterson, Charles-Francois Natali, Emil Kattainen, Fabian Meumertzheim, James Broadhead, jheaff1, kshyanashree, Noa Resare, Philipp Schrader, Shuai Zhang, Xavier Bonaventura.
{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
