| commit | 899e2595efa50ebad3b9edca58b2b6469909e48a | [log] [tgz] |
|---|---|---|
| author | Bazel Release System <noreply@google.com> | Fri Jun 21 19:07:05 2024 +0200 |
| committer | Florian Weikert <fwe@google.com> | Fri Jun 21 19:07:05 2024 +0200 |
| tree | 7ef206a23ab2ddff24402840cfe235f265e44893 | |
| parent | 08ef9b200d1b62ed66e10d89d32c709b70e7adbd [diff] |
Release 8.0.0-pre.20240607.2 (2024-06-21)
Baseline: 08ef9b200d1b62ed66e10d89d32c709b70e7adbd
Incompatible changes:
- path attribute is removed from filegroup
Important changes:
- Git merge conflicts in `MODULE.bazel.lock` files can be resolved
automatically. See
https://bazel.build/external/lockfile#automatic-resolution for
the required setup.
- Deleted Bazel's builtin aar_import helper tools. They live in
rules_android now.
This release contains contributions from many people at Google, as well as dependabot[bot], Fabian Meumertzheim, Greg Magolan, Matthieu MOREL, Ted.
{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
