commit | e9bc5ec532e681694a6bff11d6f208dce5ff7143 | [log] [tgz] |
---|---|---|
author | Bazel Release System <noreply@google.com> | Thu Mar 21 18:04:03 2024 +0000 |
committer | iancha1992 <heec@google.com> | Thu Mar 21 18:04:03 2024 +0000 |
tree | e5657879d6bf3bad22fc954a51350f76b9dd0685 | |
parent | 3e4e2af78d5b7d210094acfe43abdda23b185be1 [diff] |
Release 7.1.1 (2024-03-21) Baseline: 9b39ccaa33069c9f5688bef477abcd75e4378f04 Release Notes: + Release 7.1.0 (2024-03-11) + Update centos7 platform in build_bazel_binaries.yml (#21644) + Fix `bazel mod tidy` failure with no changes (#21662) + Update .bazelversion to 7.1.0 (#21664) + Let native Turbine image find `ct.sym` with non-hermetic `java_runtime` (#21670) + Actually use shouldPublish() to determine whether to publish the execution log to the BEP. (#21671) + Also inject a failure for createWritableDirectory when testing that ActionOutputDirectoryHelper propagates exceptions. (#21683) + Fix race condition and add more logging for null entry error message (#21692) + Allow any canonical repo name to be used with `bazel mod show_repo` (#21694) + Fix two `bazel mod tidy` crashes (#21700) + Cherry-pick Java execution info improvements (#21703) + Disable //src/test/shell/bazel:srcs_test on Intel macOS (#21707) + Fix sandbox cleanup crashing after server restart (#21733) + Revert "Fix `bazel fetch` by replacing query with cquery for … (#21735) Acknowledgements: This release contains contributions from many people at Google, as well as bazel.build machine account, Fabian Meumertzheim, Xùdōng Yáng.
{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