| commit | fc3c6fc7274603f07865f2c9ce40599522fc4f4c | [log] [tgz] |
|---|---|---|
| author | Bazel Release System <noreply@google.com> | Wed Mar 02 17:40:13 2022 +0100 |
| committer | fweikert <fwe@google.com> | Wed Mar 02 17:40:13 2022 +0100 |
| tree | f39c0d54b020d592e9b84a443b86e2b66624fe64 | |
| parent | 24e82426e689853b0d9a04e7b9b6f13e145cf2d6 [diff] |
Release 6.0.0-pre.20220223.1 (2022-03-02)
Baseline: 24e82426e689853b0d9a04e7b9b6f13e145cf2d6
Important changes:
- Include more information about configurations in cquery proto
formatted output. This deprecates the configuration field of
AnalysisProtosV2.ConfiguredTarget, and adds a new field,
configuration_id, to
be used instead.
- experimental cc_library.implementation_deps inverted to
interface_deps
- In aquery and cquery proto output, indicate if a configuration is
a
tool or non-tool configuration.
- Include complete configurations in cquery proto output.
- experimental cc_library.implementation_deps inverted to
interface_deps
This release contains contributions from many people at Google, as well as Benjamin Peterson, Keith Smiley, Mostyn Bramley-Moore, Sven Tiffe.
{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
