| commit | 7868dba6f63be95a03a1bb7051c28ec49192b70a | [log] [tgz] |
|---|---|---|
| author | Bazel Release System <noreply@google.com> | Mon Sep 27 13:05:44 2021 +0200 |
| committer | fweikert <fwe@google.com> | Mon Sep 27 13:05:44 2021 +0200 |
| tree | 9fc4cfaf1158052c5b24f32b3844b17cebd7755b | |
| parent | 11f1a6d3ce529a63d4b7111c62ae504ceac2a019 [diff] |
Release 5.0.0-pre.20210921.1 (2021-09-27)
Baseline: 11f1a6d3ce529a63d4b7111c62ae504ceac2a019
Incompatible changes:
- Remove --bep_publish_used_heap_size_post_build
- JSON trace profile: rename counter names.
Important changes:
- Adds --experimental_existing_rules_immutable_view flag to make the
native.existing_rule and native.existing_rules functions more
efficient by
returning immutable, lightweight dict-like view objects instead
of mutable
dicts.
This release contains contributions from many people at Google, as well as Wren Turkal.
{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
