commit | 0dc817cbe2bcfb14d6863e40dc06c115135e673b | [log] [tgz] |
---|---|---|
author | Bazel Release System <noreply@google.com> | Wed Oct 20 21:00:45 2021 +0200 |
committer | fweikert <fwe@google.com> | Wed Oct 20 21:00:45 2021 +0200 |
tree | 868bc1ff70183554c22ab0bd3f2719432ce56870 | |
parent | 26e7021c77cbe93730f199687091bc7cc5c23982 [diff] |
Release 5.0.0-pre.20211011.2 (2021-10-20) Baseline: 3b3bad9e774891856c198738c46d547de954b84a Cherry picks: + d8c23189c9118f99cfc3eaac98976b7c6fdacae0: Automated rollback of commit 2571ce2d9e72ee60326ef524fee1702cb2dd07e7. Incompatible changes: - Removed --action_graph from the dump command. - Remove `--{experimental_,}json_trace_compression` option. Important changes: - The --experimental_existing_rules_immutable_view flag has been renamed to --incompatible_existing_rules_immutable_view This release contains contributions from many people at Google, as well as Alex Eagle, hvadehra, Keith Smiley, Torgil Svensson, Yuval.
{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