| commit | af0e48f26b1a69b3e23cb55b026be5bd7cbedd6f | [log] [tgz] |
|---|---|---|
| author | Bazel Release System <noreply@google.com> | Tue Aug 02 17:27:10 2022 +0200 |
| committer | fweikert <fwe@google.com> | Tue Aug 02 17:27:10 2022 +0200 |
| tree | c52965d230a55744e3e378682de7e8f418b753c9 | |
| parent | 0be3eaed4dbd9e89d2717844876813664f9c405a [diff] |
Release 6.0.0-pre.20220720.3 (2022-08-02)
Baseline: 4cd266aa1dfa53d8c8de44f7895edcfd46f74725
Cherry picks:
+ f706da832996ab30ddd8784f2af697a3bb62852b:
Requires delayed release
Important changes:
- Added new register_{execution_platforms,toolchains} directives to
the MODULE.bazel file, to replace the
{execution_platforms,toolchains}_to_register attributes on the
module() directive.
- The legacy pkg_tar no longer supports the ability to untar and
repackage an input tar file (`deps` attribute). Users needed that
capability must switch to github.com/bazelbuild/rules_pkg.
This release contains contributions from many people at Google, as well as Emil Kattainen, Jason Tan, Keith Smiley, Luis Fernando Pino Duque, rustberry, Son Luong Ngoc, Yannic Bonenberger, Yannic.
{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
