commit | 20cc9ef775d46eb79a761f683b1973396a8ecf07 | [log] [tgz] |
---|---|---|
author | Bazel Release System <noreply@google.com> | Thu Jul 21 17:15:12 2022 +0200 |
committer | fweikert <fwe@google.com> | Thu Jul 21 17:15:12 2022 +0200 |
tree | b7750ea4f2f70abde4e6467d912d8779aafab980 | |
parent | 1e7127dec96b69b8cd5d332551f8798433d6057e [diff] |
Release 6.0.0-pre.20220706.4 (2022-07-21) Baseline: ea8b99cf2a5914c67e4bd7651d83df98912bb1ed Cherry picks: + 107a54edcf75dc026cf643df82c13fe32a1eb043: Fix flag file regexp broken by https://github.com/bazelbuild/bazel/commit/cb2cd9fd2b65311da92777 7c35939701add5b879. + 1e7127dec96b69b8cd5d332551f8798433d6057e: Reinstate legacy worker flag file behaviour when not using --experimental_worker_strict_flagfiles. Incompatible changes: - Flag --experimental_local_memory_estimate removed. This release contains contributions from many people at Google, as well as Fabian Meumertzheim, Tomas Volf, 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