| commit | a5a9c8326d36a5132cf24fc7ea01e42977a42266 | [log] [tgz] |
|---|---|---|
| author | Bazel Release System <noreply@google.com> | Thu Dec 08 17:18:28 2022 +0100 |
| committer | fweikert <fwe@google.com> | Thu Dec 08 17:18:28 2022 +0100 |
| tree | aa731e6ba4a79a98635b7f8149fb2a9a68c10e50 | |
| parent | 14e32e7f5d1492f7ca4ffc17c40b913ec5799603 [diff] |
Release 7.0.0-pre.20221123.2 (2022-12-08)
Baseline: 14e32e7f5d1492f7ca4ffc17c40b913ec5799603
Incompatible changes:
- the --experimental_async_execution flag is now a no-op.
New features:
- The `aquery` and `cquery` commands now respect the
`--query_file` flag just like the `query` command.
Important changes:
- Starlark `print()` statements are now emitted iff the line of
code is executed. They are no longer replayed on subsequent
invocations unless the Starlark code is re-executed.
Additionally, multiple identical `print()` statements (same
string from the same line of code, e.g. from a loop) are all
emitted and no longer deduplicated.
This release contains contributions from many people at Google, as well as Benjamin Peterson, Christopher Sauer, Daniel KT, Fabian Meumertzheim, Matt Mackay.
{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
