commit | f32f2c1bd2c40bfd12de37cc275fdceda0ffd731 | [log] [tgz] |
---|---|---|
author | Bazel Release System <noreply@google.com> | Thu Oct 03 14:26:30 2024 +0000 |
committer | keertk <keerthanakumar@google.com> | Thu Oct 03 14:26:30 2024 +0000 |
tree | b8cb2488c7e57581cd623abc2b96b5b77f892f3c | |
parent | bb3f3299e1c9cdab39aa70c1c773de4f630c57b5 [diff] |
Release 8.0.0-pre.20240925.4 (2024-10-03) Baseline: f4d92d45be3617b72c21ad5ce8912fa548472e50 Cherry picks: + 99434b16ba41677b92f7eb79d5d8dcb1130d7c47: Automated rollback of commit 4607ad439fe8869c8e8951d953e2d3adb613e6d6. Incompatible changes: - `ctx.resolve_tools` is no longer available by default, in preparation for complete removal. See https://github.com/bazelbuild/bazel/issues/22249 for migration instructions. Use `--noincompatible_disallow_ctx_resolve_tools` to temporarily make it available again. - The `aquery` command now reports all potential inputs of actions that support input discovery, including the input headers of C++ compilation actions and those explicitly marked as unused through the `unused_inputs_list` argument to `ctx.actions.run`. Set `--noinclude_pruned_inputs` to omit pruned inputs from `aquery` output when running it after action execution. RELNOTES[INC]: This is not a release note, but a reminder to remove the note for `--include_scheduling_dependencies`, which was introduced in the 8.x tree but won't make it into the final release. - `--zip_undeclared_test_outputs` now defaults to false, causing undeclared test outputs (i.e., files written to `$TEST_UNDECLARED_OUTPUTS_DIR` by a test) to be produced as a directory instead of a zip file. - --legacy_important_outputs is flipped to false. See #14353 for details New features: - Bazel can now parse .scl files, a dialect of Starlark without Bazel-specific symbols. - Dormant dependencies and materializer functions are now available with the --experimental_dormant_deps flag. Important changes: - Deleted native Android mobile-install - Repository rules instantiated in the same module extensions can now refer to each other by their extension-specified names in label attributes. - A new experimental flag, `--experimental_build_event_output_group_mode`, allows users to change how a given output group's files are reported in BEP. The current behavior is `FILESET` which populates `OutputGroup.file_sets`. Users may now specify `INLINE` to instead report files directly in the `TargetComplete`/`AspectComplete` event under `OutputGroup.inline_files`. Users may also specify `BOTH` to populate `OutputGroup.file_sets` and `OutputGroup.inline_files`. - Bazel no longer has the android_binary, android_library, android_device_script_fixture and android_host_service_fixture rules. Use https://github.com/bazelbuild/rules_android instead. See https://github.com/bazelbuild/bazel/issues/23199 - Bazel no longer has the android_sdk_repository rule. Use https://github.com/bazelbuild/rules_android instead. - Uploading local action results to a disk or remote cache now occurs in the background whenever possible, potentially unblocking the execution of followup actions. Set `--noremote_cache_async` to revert to the previous behavior. - `--incompatible_remote_downloader_send_all_headers` is removed. - `--build_event_upload_max_threads` is removed. - `incompatible_remote_output_paths_relative_to_input_root` is removed. - The default value of `--experimental_remote_cache_compression_threshold` is changed to `100`. - Build without the Bytes is disabled when using HTTP cache. - Build without the Bytes is disabled when using HTTP cache. - Symlink trees are now created through direct filesystem calls by default, instead of delegated to a helper process. On Windows, this entails respecting the `--windows_enable_symlinks` flag, falling back to a copy when the flag is unset (the helper process always attempts to create symlinks, irrespective of the flag). Set `--noexperimental_inprocess_symlink_creation` to temporarily revert to the previous behavior, which will be removed in a future release. - By default, coverage artifacts will be reported inline in the `TargetComplete` event. To disable this behavior, pass `--experimental_build_event_output_group_mode=baseline.lcov=named_ set_of_files_only`. - Uploading local action results to a disk or remote cache now occurs in the background whenever possible, potentially unblocking the execution of followup actions. Set `--noremote_cache_async` to revert to the previous behavior. - Overrides in the root MODULE.bazel file are now ignored with `--ignore_dev_dependency`. (Overrides in non-root modules are already ignored.) - Added support for using a remote cache that evicts blobs and doesn't have AC integrity check (e.g. HTTP cache). - Undeclared test outputs are now reported individually in the BEP, unless zipping is enabled via `--zip_undeclared_test_outputs`. - The native version of android_tools_defaults_jar is no longer in Bazel. Use https://github.com/bazelbuild/rules_android instead. - Bazel fetch and vendor command now supports --target_pattern_file for specifying target patterns. - The compact execution log now stores runfiles in a more compact representation that should reduce the memory overhead and log output size, in particular for test spawns. This change required breaking changes to the (experimental) log format. - `override_repo` and `inject_repo` can be used to override and inject repos in module extensions. - Patches to the module file in `single_version_override` are now effective as long as the patch file lies in the root module. - If `--allowed_cpu_values` is set, the `--cpu` flag value is validated against it. This release contains contributions from many people at Google, as well as Adam Azarchs, Alessandro Patti, Benjamin Peterson, Cornelius Riemenschneider, dependabot[bot], Fabian Meumertzheim, Fil-Den, George Gensure, hvd, Jacob Van De Weert, James Sharpe, Javier Maestro, Jay Conrod, John Millikin, Jordan Mele, Jordan Mele, Keith Smiley, Lior Gorelik, Luis Padron, Michael Siegrist, Nils Wireklint, PikachuHy, Sangita.Nalkar, Son Luong Ngoc, Thi Doan, Xdng Yng, xinyu.wang.
{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