| commit | 67f0a49cb766cb2ae8985f45091eded8415ad6ec | [log] [tgz] |
|---|---|---|
| author | Bazel Release System <noreply@google.com> | Thu Aug 15 14:14:25 2024 +0000 |
| committer | keertk <keerthanakumar@google.com> | Thu Aug 15 14:14:25 2024 +0000 |
| tree | 7c8849e3141ab10ecfb80ed785d5bf7ffb0a90b8 | |
| parent | 133eb60925496e3153bcc7903968b4eeb6d16068 [diff] |
Release 8.0.0-pre.20240812.1 (2024-08-15)
Baseline: 133eb60925496e3153bcc7903968b4eeb6d16068
New features:
- aspects can now return DefaultInfo, which will then be merged
with that of the configured target they are applied to.
Currently, only the files= field is supported.
Important changes:
- BEP will include correct \`TestResult\` and \`TargetSummary\`
events when special test inputs like \`$test_runtime\` fail to
build.
- Improve progress message in case there are no actions in flight,
and display explicitly "no actions running" in that case.
- The new `cc_static_library` rule produces a static library that
bundles given targets and all their transitive dependencies. It
has to be enabled via `--experimental_cc_static_library`.
This release contains contributions from many people at Google, as well as Fabian Meumertzheim, FaBrand, Jiawen (Kevin) Chen, Son Luong Ngoc, Victor Hiairrassary.
{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
