| commit | 8f6c032e6b0f2f008351c674e56d6f71150f8a9d | [log] [tgz] |
|---|---|---|
| author | Bazel Release System <noreply@google.com> | Mon Apr 17 21:20:02 2023 +0200 |
| committer | fweikert <fwe@google.com> | Mon Apr 17 21:20:02 2023 +0200 |
| tree | ec9384bca0801e219a2542e1eb5ff9ae2222c29d | |
| parent | 237fb69ede58a7cb672363451c2cb455637fccfe [diff] |
Release 7.0.0-pre.20230410.1 (2023-04-17)
Baseline: 237fb69ede58a7cb672363451c2cb455637fccfe
Incompatible changes:
- Remove high priority workers functionality from blaze.
Important changes:
- `--experimental_remote_build_event_upload` has been renamed to
`--remote_build_event_upload`
- [Breaking change] platform, constraint_setting, and
constraint_value can no longer take an applicable_licenses value.
Remediation is to remove the attribute and rely on the package
level default.
This release contains contributions from many people at Google, as well as Brentley Jones, Fabian Meumertzheim, Philipp Schrader, Ulf Adams, 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
