commit | 6f70c5dbfc200179431a57c8f31b155254196be5 | [log] [tgz] |
---|---|---|
author | Bazel Release System <noreply@google.com> | Fri May 31 17:58:21 2024 +0200 |
committer | Florian Weikert <fwe@google.com> | Fri May 31 17:58:21 2024 +0200 |
tree | a18358078b770410684bc04b57dfb24e19f219f1 | |
parent | 3e7dfb7258d6fcaf92142c91f8dfc3c45741652a [diff] |
Release 8.0.0-pre.20240523.3 (2024-05-31) Baseline: 739f7b83e02fb8f17c1a498630c7e02701d83aa1 Cherry picks: + cdd104c714dfcdf2661f900ba3c5ebf3616884bb: Do not record events announced after the build-completing event. + b12f536902594e48655c310d62c0bd069484798b: Integrate the skymeld cases into the rewinding inconsistency receiver. Incompatible changes: - The --experimental_aquery_dump_after_build_format and --experimental_aquery_dump_after_build_output_file command line options are not available anymore. Important changes: - Paths in the Linux sandbox are now again identical to those outside the sandbox, even with `--incompatible_sandbox_hermetic_tmp`. - `cc_toolchain` now passes runfiles for its *_files attrs (e.g. data files for a tool built for linking). - `Label` instances passed to `print` or `fail` as positional arguments are now formatted with apparent repository names (optimized for human readability). This release contains contributions from many people at Google, as well as Fabian Meumertzheim, George Gensure, Greg Magolan, hvd, Isaac Torres, Keith Smiley, oquenchil, Tobias Werth, Tomasz Pasternak, UebelAndre, Xdng Yng.
{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