| commit | 9f8994e4e51efbeb199a05cdf7a31466aa40572d | [log] [tgz] |
|---|---|---|
| author | Bazel Release System <noreply@google.com> | Thu Feb 02 22:56:46 2023 +0100 |
| committer | fweikert <fwe@google.com> | Thu Feb 02 22:56:46 2023 +0100 |
| tree | fc88aeaad056d1f697d46b6587012ede85888c48 | |
| parent | b4134895912a29a420173034f4b7c044e80a74fd [diff] |
Release 7.0.0-pre.20230123.5 (2023-02-02)
Baseline: 2f9c7d60ea676f9f8e929b20a3ff74e786995c91
Cherry picks:
+ 9d92e7189bd7996286cbc0b04ae5c3ef7894f23c:
Small tweaks to platform documentation. - Point platform rules
to the explanatory document which people should have read first.
- Update the left nav to include the word "Toolchains" - move
https://bazel.build/extending/platforms from Design Docs to
Concepts
+ d5095dbfd320654298aaa1b412a7581b53792d3f:
"bazel config" output tests: skip noconfig.
+ 923425002daae6f83cb0c6487cc3453b2dc89a43:
Automated rollback of commit
0fe4c36a7feb24444bc72731bf4839aa1ca926c6.
Incompatible changes:
- --experimental_build_transitive_python_runfiles is flipped to
false. See #16303 for details
Important changes:
- Now that the host configuration is finished, `genrule` should
prefer the use of `tools` and stop using `exec_tools`.
This release contains contributions from many people at Google, as well as Fabian Meumertzheim, Keith Smiley.
{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
