| commit | 4e90ad71b1422334947efbf70bb940dc199e5dab | [log] [tgz] |
|---|---|---|
| author | Bazel Release System <noreply@google.com> | Mon Dec 20 17:46:20 2021 +0100 |
| committer | fweikert <fwe@google.com> | Mon Dec 20 17:46:20 2021 +0100 |
| tree | 3739dd5d1cfa936088ba61febb72f9c19a8e20da | |
| parent | c77dad63df138fbc3ebe6983563e9f3453db8cb2 [diff] |
Release 6.0.0-pre.20211202.4 (2021-12-20)
Baseline: 00a3354d54752648fc81a8c7277775780a05f5f2
Cherry picks:
+ c873525af9e045c87dfca2ac82ca68e9b76f8820:
Extract out constant for "current time" magic value in
Path#setLastModifiedTime, to avoid confusion.
+ 7074bcff7d1fcba7230fec11ce1d155b6e3d51b1:
Automated rollback of commit
ed825a49ef18a87e75fcbc381bb9b656e83b04fb.
Important changes:
- alias() can now select() directly on constraint_value()
This release contains contributions from many people at Google, as well as Brentley Jones, Chris Fredrickson, Danny Wolf, Dimi Shahbaz, Ed Schouten, Fabian Meumertzheim, Fredrik Medley, Greg Estren, hvadehra, Noa Resare, Simon Bjorklen, Tetsuo Kiso.
{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
