commit | 690913d90be79c11e29019521db83fd5ffeb709f | [log] [tgz] |
---|---|---|
author | Bazel Release System <noreply@google.com> | Thu Dec 01 13:01:57 2022 +0100 |
committer | fweikert <fwe@google.com> | Thu Dec 01 13:01:57 2022 +0100 |
tree | a356cabd4acdd5f538b0b0e07ce5c99155f31d45 | |
parent | b32ae70579cffa2cd25316f6cf355e9ee86f6b3e [diff] |
Release 7.0.0-pre.20221111.3 (2022-12-01) Baseline: 455454a56e961affb041a1d4a9214f7f313a05aa Cherry picks: + 4caae75b49e815ad2cf1d805f316bc374f03f2ae: Automated rollback of commit 8f956511bb115c39ac683a1e78971fcf9dce5deb. Important changes: - The new path variable `$(rlocationpath ...)` and its plural form `$(rlocationpaths ...)` can be used to expand labels to the paths accepted by the `Rlocation` function of runfiles libraries. This is the preferred way to access data dependencies at runtime and works on all platforms, even when runfiles are not enabled (e.g., on Windows by default). This release contains contributions from many people at Google, as well as Ankush Goyal, Artem Zinnatullin, Christopher Peterson Sauer, Ed Schouten, Fabian Meumertzheim, Greg Magolan, keertk, Keith Smiley, nathyong, Robin Tweedie, Yannic Bonenberger, Yannic.
{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