| commit | 9f0a0c5719c2247aedd7bed0c6b8e59726a9e613 | [log] [tgz] |
|---|---|---|
| author | Bazel Release System <noreply@google.com> | Thu Apr 25 18:08:18 2024 +0200 |
| committer | Florian Weikert <fwe@google.com> | Thu Apr 25 18:08:18 2024 +0200 |
| tree | c09c8a60a79a5b58df570969e73b3cb8366dc1f8 | |
| parent | 1115e526662c041214aecb3b4c9550b91f79275a [diff] |
Release 8.0.0-pre.20240415.1 (2024-04-25)
Baseline: 1115e526662c041214aecb3b4c9550b91f79275a
Important changes:
- toolchain type requirements of rules are now treated as implicit
dependencies in `bazel query`. This includes those defined via
the `toolchains` parameter of starlark `rule()` definitions.
- Starlark `min` and `max` buitins now allow a `key` callback,
similarly to `sorted`.
This release contains contributions from many people at Google, as well as Alexandre Boulgakov, Brentley Jones, Cameron Martin, Emil Waijers, Fabian Meumertzheim, Xdng Yng.
{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
