| commit | b667b6eae4b6a85cf67c4c89d49d0d0fd568e6b0 | [log] [tgz] |
|---|---|---|
| author | Bazel Release System <noreply@google.com> | Wed Aug 30 20:36:06 2023 +0200 |
| committer | fweikert <fwe@google.com> | Wed Aug 30 20:36:06 2023 +0200 |
| tree | ff0612804e5e02f2d70bd6f4edf495a01e8c329e | |
| parent | 417fd1359d69cfacd4a2a8f6f7c2b113face5dca [diff] |
Release 7.0.0-pre.20230823.4 (2023-08-30)
Baseline: d55c11b658255a4574e0b3eb50d76dd6123866e6
Cherry picks:
+ 34c5ef22e88eba60238ad3735b74ea71db1c993e:
make sure IdempotencyChecker use the correct rule transition and
remove redundant computeTransition calls.
+ 32d018ea402a5acbb574b7f4bf600b3cc040778c:
Make targets in analysis completed events visible.
Incompatible changes:
- The --apple_compiler command line option is not available anymore.
- py_transitions top-level was removed.
Important changes:
- Android resources will no longer propagate through neverlinked
libraries by default.
This release contains contributions from many people at Google, as well as Alex Eagle, arun.sampathkumar, Benjamin Lee, Fabian Meumertzheim, Gunnar Wagenknecht, Julio Merino, Keith Smiley, Nicholas Junge.
{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
