| commit | 69754d7b65df53ed5e48ca67f3c741fc21984d80 | [log] [tgz] |
|---|---|---|
| author | Bazel Release System <noreply@google.com> | Tue Nov 14 23:54:10 2023 +0100 |
| committer | fweikert <fwe@google.com> | Tue Nov 14 23:54:10 2023 +0100 |
| tree | 8a94a11b42f8c72e96325b9f9c65e971f452475e | |
| parent | a18175e891dda22d61c9fed3e9b8e726881d9704 [diff] |
Release 8.0.0-pre.20231030.2 (2023-11-14)
Baseline: 8cab6aa21fa765985a962e59264e12251e4d479f
Cherry picks:
+ d78bdd2f7143da31087c3ab88298b52defb90fdc:
Temporarily disable `BaselineOptionsFunction` + Starlark exec
transition.
Incompatible changes:
- Java runtime toolchains created via `local_java_repository` from
`@bazel_tools//tools/jdk:local_java_repository.bzl`, which
includes `local_jdk`, now have `target_compatible_with` set to
the auto-detected host constraints. This can result in errors
about toolchain resolution failures for
`@bazel_tools//tools/jdk:runtime_toolchain_type`, especially when
cross-compiling. These failures can be fixed in the following
ways (listed in decreasing order of preference):
* Replace `java_binary` targets that aren't meant to be run with
`bazel run` or as tools during the build with `java_single_jar`
(available in `@rules_java//java:java_single_jar.bzl`). Such
targets do not require a Java runtime for the target
configuration.
* Set `--java_runtime_version=remotejdk_N` for some Java version
`N` to let Bazel choose and download an appropriate remote JDK
for the current target platform. This setting defaults to
`local_jdk`, which means that Bazel can only use the local JDK,
which isn't compatible with any other platform.
* Manually define and register a `local_java_runtime` with no
value set for `exec_compatible_with` (defaults to `[]`) and
select it by setting `--java_runtime_version` to its `name`. This
fully restores the previous behavior, but can result in incorrect
results when cross-compiling (see #18265).
- transition is removed from objc_library
(https://github.com/bazelbuild/bazel/issues/19688)
New features:
- "bazel aquery" now returns the headers C++ compilation actions
can include if the --include_scheduling_dependencies command line
option is set.
Important changes:
- Enable Platforms and Toolchains for Android. Android projects
will need to stop passing the legacy flag `--fat_apk_cpu`, and
instead use `--android_platforms` using platforms defined with
the `@platforms//os:android` constraint. The
https://github.com/bazelbuild/rules_android repository defines
four standard Android platforms for projects that use those
rules, `@rules_android//:armeabi-v7a`,
`@rules_android//:arm64-v8a`, `@rules_android//:x86`,
`@rules_android//:x86_64`.
This release contains contributions from many people at Google, as well as Benjamin Peterson, Fabian Meumertzheim, Fredrik Medley, Guillaume Maudoux, Ulf Adams, Wade Carpenter.
{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
