| commit | 731478175b5af2899c7dcbfcd6170659b139d913 | [log] [tgz] |
|---|---|---|
| author | Bazel Release System <noreply@google.com> | Thu Feb 16 19:55:44 2023 +0100 |
| committer | fweikert <fwe@google.com> | Thu Feb 16 19:55:44 2023 +0100 |
| tree | 8a9578974551089d966a006ddc251afde9f09055 | |
| parent | a4d6e9f089755a5aa34dbfb4adfe1d1181e12317 [diff] |
Release 7.0.0-pre.20230209.2 (2023-02-16)
Baseline: 66121a75d67b92990966fc94771a22b0b4a062e3
Cherry picks:
+ 534089ed10a253b31c499a284079f52a92bc0347:
Automated rollback of commit
02b1b78f0278e2d6d9f294b9cfe86f72f0c9a900.
Incompatible changes:
- --incompatible_python_disable_py2 is flipped to true. See #17293
for details.
Important changes:
- Added a `native.package_relative_label()` function, which
converts a label string to a Label object in the context of the
calling package, in contrast to `Label()`, which does so in the
context of the current .bzl file. Both functions now also accept
relative labels such as `:foo`, and are idempotent.
This release contains contributions from many people at Google, as well as Benjamin Lee, Benjamin Peterson, Chirag Ramani, Ezekiel Warren, Fabian Meumertzheim, Jon Parise, jonrose-dev, keertk, Sara Adams, yuzhy8701.
{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
