| commit | c547b713664bdc7c22787178294dff11cd72424a | [log] [tgz] |
|---|---|---|
| author | Bazel Release System <noreply@google.com> | Thu Mar 07 20:04:04 2024 +0100 |
| committer | Florian Weikert <fwe@google.com> | Thu Mar 07 20:04:04 2024 +0100 |
| tree | 4e950ad114f89fc40c593d11cb607e522ee85d91 | |
| parent | 7f749e927f61a84ef3a8f361ce601db9d2b81fc4 [diff] |
Release 8.0.0-pre.20240303.1 (2024-03-07)
Baseline: 7f749e927f61a84ef3a8f361ce601db9d2b81fc4
New features:
- New $(DUMPBIN) make variable is now available for Visual Studio
toolchains.
Important changes:
- The result of `canonicalize-flags` now includes all Starlark
flags by default. Use `--noexperimental_include_default_values`
for the old behavior that only reports Starlark flags with
non-default values.
- Added `windows_quoting_for_param_files` feature for windows-style
parameter file escaping.
This release contains contributions from many people at Google, as well as Alex Sharoff, Cameron Martin, Cristin Donoso, Son Luong Ngoc, Sushain Cherivirala, Viktor Kustov, Yannic Bonenberger.
{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
