| commit | abd96fc196d3cee09beb075eb819c470753ad0a6 | [log] [tgz] |
|---|---|---|
| author | Bazel Release System <noreply@google.com> | Fri Jan 28 14:48:49 2022 +0100 |
| committer | fweikert <fwe@google.com> | Fri Jan 28 14:48:49 2022 +0100 |
| tree | b51ac6884384f6f304450a2bf6ab70f9e60450f6 | |
| parent | e2abe2b519fe86b213d822c1fadd7a51d6d3a3f6 [diff] |
Release 6.0.0-pre.20220123.2 (2022-01-28)
Baseline: e2abe2b519fe86b213d822c1fadd7a51d6d3a3f6
Incompatible changes:
- Error Prone now checks for unused return values of additional
methods on `java.lang.Object`, which can be disabled using
`--javacopts=-Xep:ReturnValueIgnored:OFF`
- Error Prone now checks for unused return values of additional
methods on `java.lang.Object`, which can be disabled using
`--javacopts=-Xep:ReturnValueIgnored:OFF`
Important changes:
- provider() has a new parameter: init, a callback for performing
pre-processing and validation of field values. Iff this parameter
is set,
provider() returns a tuple of 2 elements: the usual provider
symbol (which,
when called, invokes init) and a raw constructor (which bypasses
init).
This release contains contributions from many people at Google, as well as Chad Miller, Christopher Sauer, dmaclach, floriographygoth, jheaff1, juanchoviedo, Keith Smiley, Oscar Bonilla, Paul Tarjan, Ulrik Falklof, Zhongpeng Lin.
{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
