| commit | cf30e4c4b95da903adc2b272ff9b55a310c2d0a9 | [log] [tgz] |
|---|---|---|
| author | Bazel Release System <noreply@google.com> | Wed May 03 21:05:13 2023 +0200 |
| committer | fweikert <fwe@google.com> | Wed May 03 21:05:13 2023 +0200 |
| tree | 139559a74b505dbe7f6597d8d61ff5d242c88636 | |
| parent | dc724e4e8041a9357c6b82af0749def4174f21f2 [diff] |
Release 7.0.0-pre.20230426.1 (2023-05-03)
Baseline: dc724e4e8041a9357c6b82af0749def4174f21f2
Important changes:
- Added a new `max_compatibility_level` attribute to the
`bazel_dep` directive, which allows version selection to upgrade
a dependency up to the specified compatibility level.
- `--experimental_remote_grpc_log` has been renamed to
`--remote_grpc_log`
- `--incompatible_remote_build_event_upload_respect_no_cache` is
now a no-op.
This release contains contributions from many people at Google, as well as Benjamin Peterson, Brentley Jones, Fabian Meumertzheim, George Gensure, Kai Zhang, Oscar Garzon.
{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
