| commit | cf294c3d6ded195be618cc4fd5896159264a71f0 | [log] [tgz] |
|---|---|---|
| author | Bazel Release System <noreply@google.com> | Thu Feb 15 16:44:47 2024 +0100 |
| committer | fweikert <fwe@google.com> | Thu Feb 15 16:44:47 2024 +0100 |
| tree | 2522fbc1b40d04454e54660788b9a0c44efa664f | |
| parent | 6c20e16d796fa0f73e7afe9b1a53cef1eaac4d45 [diff] |
Release 8.0.0-pre.20240206.3 (2024-02-15)
Baseline: cc8be0ab496570eb155ba220012f52f6a6c7082d
Cherry picks:
+ cff79d0aa6f2d470b8648f2b89beeefd0867e177:
Do not build the runfiles tree when creating deploy jars.
+ 959ab10559800eab6a3841f80cbc06f119e659b7:
Fix bug in GraphOutputWriter#partitionedFactored which caused
queue to grow to O(E), and now upper-bounding it to O(N).
Incompatible changes:
- The --host_jvm_profile command line argument is not supported
anymore.
- The "input_manifests" argument of ctx.actions.{run,run_shell} is
now a no-op. resolve_command and resolve_tools always return the
empty list as the input manifest list.
Important changes:
- Bazel's Bash completion can now complete external repository
labels when using `--enable_bzlmod`.
- BEP's `execution_phase_time_in_ms` no longer includes the
analysis-only part at the beginning of the build. Artificial
downtrend in `execution_phase_time_in_ms` expected.
This release contains contributions from many people at Google, as well as Fabian Meumertzheim, Xdng Yng, Zheng Wei Tan.
{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
