| commit | 396cc85a6c331a404875542e03d009b7708451f1 | [log] [tgz] |
|---|---|---|
| author | Bazel Release System <noreply@google.com> | Mon May 23 23:41:35 2022 +0200 |
| committer | fweikert <fwe@google.com> | Mon May 23 23:41:35 2022 +0200 |
| tree | 2dd8e5a5b39999aa573788dde4b4e7a82be5027d | |
| parent | 61fd06d92706d64fbcef64f0f54cded91c88afff [diff] |
Release 6.0.0-pre.20220517.1 (2022-05-23)
Baseline: 61fd06d92706d64fbcef64f0f54cded91c88afff
Incompatible changes:
- Split up the C++ archive from the C++ link action and set
`CppArchive` as mnemonic.
Important changes:
- Switch cc_test implementation to Starlark. Note: cc_test will now
link statically when _targeting_ Windows regardless of host
platform (rather
than always linking statically when Windows is the _host_).
- Bazel uses the D8 jar from Maven instead of the SDK.
- "blaze config" now only reports info from the last build. To
compare configurations across multiple builds, redirect "blaze
config" output to a file and run your favorite diff tool.
- The --incompatible_override_toolchain_transition flag is now
always set, and will be removed in the future. Thus,
--noincompatible_override_toolchain_transition has no effect, and
the value of the incompatible_use_toolchain_transition parameter
in aspect() and rule() builtins is ignored.
- Switch cc_test implementation to Starlark. Note: cc_test will now
link statically when _targeting_ Windows regardless of host
platform (rather
than always linking statically when Windows is the _host_).
- Toolchain types may now be optional, in addition to mandatory.
See https://bazel.build/docs/toolchains#optional-toolchains for
further details.
This release contains contributions from many people at Google, as well as Andreas Fuchs, Andrew Klotz, Benjamin Lee, Benjamin Peterson, Chris Clearwater, Christopher Peterson Sauer, Christopher Sauer, Daniel Wagner-Hall, Fabian Meumertzheim, Fredrik Medley, George Prekas, Grzegorz Lukasik, Halil Sener, homuler, John Laxson, John Millikin, Keith Smiley, Matt Clarkson, Peter Mounce, Philipp Schrader, Ryan Beasley, Saleem Abdulrasool, Takeo Sawada, ThomasCJY, Vladimir Tagakov, 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
