Closed renovate[bot] closed 10 months ago
I think #104 will supercede this naive update
Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 7.x
releases. But if you manually upgrade to 7.x
then Renovate will re-enable minor
and patch
updates automatically.
If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.
This PR contains the following updates:
6.5.0
->7.0.2
Release Notes
bazelbuild/bazel (bazel)
### [`v7.0.2`](https://togithub.com/bazelbuild/bazel/blob/HEAD/CHANGELOG.md#Release-702-2024-01-25) [Compare Source](https://togithub.com/bazelbuild/bazel/compare/7.0.1...7.0.2) Baseline: 2634a6ec8bef0d8eef9870b23befdddb3dbe0005 Release Notes: + Disregard WORKSPACE while verifying lockfile repo mapping entries in extension eval (#21003) Acknowledgements: This release contains contributions from many people at Google, as well as bazel.build machine account, Xdng Yng. ### [`v7.0.1`](https://togithub.com/bazelbuild/bazel/blob/HEAD/CHANGELOG.md#Release-701-2024-01-18) [Compare Source](https://togithub.com/bazelbuild/bazel/compare/7.0.0...7.0.1) Baseline: d798ebde6c6394203a87b5f1a6b62ecfc3880991 Release Notes: + Consider MODULE.bazel for workspace detection in bazel.sh (#20594) + Auto-create deploy jars for Bazel `java_test` targets if requested (#20602) + `java_binary` wrapper should forward `restricted_to` (#20611) + Mount user-specified bind mounts before Bazel's own magic. (#20609) + Fix bootstrapped Bazel binary (#20612) + Attempt to make main repo mapping inverse more efficient (#20625) + Cherry-pick all presubmit.yml changes (#20733) + Print interactive sandboxed shell command with `--sandbox_debug` (#20734) + Fix two issues with --incompatible_sandbox_hermetic_tmp that manifested themselves when the output base was under /tmp (#20718) + Let module extensions track calls to `Label()` (#20750) + Add support for bind mounts under `/tmp` with hermetic tmp (#20749) + Fixes for Bazel's own integration tests fail locally on Linux (#20821) + Fix NPE in BzlmodRepoRuleFunction (#20828) + Avoid emitting canonical labels into generated repos (#20840) + Let .bzl files record their usages of repo mapping (#20848) + Force output checking for incremental run commands without the bytes. (#20881) + Retry binding to ipv6 localhost (#20903) + Fix linker feature detection being performed on wrong linker (#20901) + Fix singlejar resource mapping for external repositories (#20904) Acknowledgements: This release contains contributions from many people at Google, as well as bazel.build machine account, David Ostrovsky, Fabian Meumertzheim, hvd, Siddhartha Bagaria, Tianyu Geng, Xdng Yng, Xùdōng Yáng. ### [`v7.0.0`](https://togithub.com/bazelbuild/bazel/blob/HEAD/CHANGELOG.md#Release-700-2023-12-11) [Compare Source](https://togithub.com/bazelbuild/bazel/compare/6.5.0...7.0.0) Baseline: d60ce2c7c86393638c77698c00c2168a7a936a53 Release Notes: + **[Incompatible]** This has the side effect of changing the message on unsuccessful builds from ``` FAILED: Build did NOT complete successfully (0 packages loaded) ``` to ``` ERROR: Build did NOT complete successfully ``` + The new path variable `$(rlocationpath ...)` and its plural form `$(rlocationpaths ...)` can be used to expand labels to the paths accepted by the `Rlocation` function of runfiles libraries. This is the preferred way to access data dependencies at runtime and works on all platforms, even when runfiles are not enabled (e.g., on Windows by default). + The `aquery` and `cquery` commands now respect the `--query_file` flag just like the `query` command. + **[Incompatible]** the --experimental_async_execution flag is now a no-op. + **[Incompatible]** --experimental_replay_action_out_err is not a no-op. + **[Incompatible]** `cquery --output=files` also outputs source files. + removed outdated ctx.host_fragments + **[Incompatible]** When multiple --deleted_packages options are passed on the command line, they will be concatenated instead of the latest one taking effect. + removed outdated ctx.host_configuration + **[Incompatible]** JSON profile: Use doubles instead of strings for counter series. + Now that the host configuration is finished, `genrule` should prefer the use of `tools` and stop using `exec_tools`. + **[Incompatible]** --experimental_build_transitive_python_runfiles is flipped to false. See #16303 for details + **[Incompatible]** --incompatible_python_disable_py2 is flipped to true. See #17293 for details. + Update Android manifest merger to v30.1.3, and also drop support for legacy (pre-D8) desugaring. + Correctly encode double value positive infinity as "inf" instead of "+inf" for textprotos. + **[Incompatible]** When remote cache evicts blobs, Bazel will exit with code 39. + Add --use_target_platform_for_tests which uses the target platform for executing tests instead of the execution platform. + **[Incompatible]** `--features` only applies to targets built in the target configuration, and `--host_features` is used for the host / exec configuration (gated behind `--incompatible_use_host_features`) + Custom C++ rules on Windows calling cc_common.create_linking_context_from_compilation_outputs should review whether each target of the rule type should produce a dynamic library since a condition which blocked their creation has been moved to the rules from behind the API. + Add flag `--experimental_remote_cache_ttl` and set the default value to 3 hours. + making --incompatible_use_platforms_repo_for_constraints do nothing. Using constraints from @bazel_tools//platforms with or without the flag will throw error with message "Constraints from @bazel_tools//platforms have been removed. Please use constraints from @platforms repository embedded in Bazel, or preferably declare dependency on https://github.com/bazelbuild/platforms" + **[Incompatible]** Bazel's local CPU resource on Linux is now container aware. Use `--local_cpu_resources`, `--loading_phase_threads` or `--jobs` to override. + Subsequent settings of --extra_execution_platforms now override previous settings, instead of adding them to a list. If you currently set --extra_execution_platforms more than once, please migrate by passing a list of values to --extra_execution_platforms instead so that earlier values aren't overwritten. + @bazel_tools//config:common_settings.bzl has been removed. Use @bazel_skylib//rules:common_settings.bzl instead. + **[Incompatible]** `copy_from_rule` is exec_groups is deprecated (https://github.com/bazelbuild/bazel/issues/17668). + cc_shared_library is no longer experimental, see https://github.com/bazelbuild/bazel/issues/16709 for details + **[Incompatible]** --legacy_bazel_java_test is now a no-op + The flag `--distinct_host_configuration` is removed. It has been a no-op since Bazel 6.0.0. + Add `--skip_incompatible_explicit_targets` option + **[Incompatible]** `--experimental_execution_graph_log` no longer exists. Current users that want local logs need to pass `--experimental_enable_execution_graph_log --experimental_execution_graph_log_path=/some/local/path`. Current users that want logs uploaded to BEP need to pass `--experimental_enable_execution_graph_log --experimental_stream_log_file_uploads`. + Remove 'darwin' as a CPU value, use 'darwin_x86_64' instead + **[Incompatible]** Remove 'darwin' as a CPU value, use 'darwin_x86_64' instead + cc_test can now be configured by using a native.toolchain(). + The location of rules that explicitly specify `generator_name` and/or `generator_function` attributes (typically because they are incidentally copied from `native.existing_rule()`) is now the top-level call in the `BUILD` file, which is consistent with rules that do not explicitly specify these attributes. + Warnings (most notably those associated with the `deprecation` rule attribute) are no longer replayed on subsequent invocations unless the target in question is re-analyzed. Warnings are purely informational, so this change has no bearing on the correctness of the build. Downstream tests that break due to this change should update their expectations. + `--experimental_remote_build_event_upload` has been renamed to `--remote_build_event_upload` + **[Incompatible]** Remove high priority workers functionality from blaze. + [Breaking change] platform, constraint_setting, and constraint_value can no longer take an applicable_licenses value. Remediation is to remove the attribute and rely on the package level default. + `--experimental_action_cache_store_output_metadata` has been renamed to `--action_cache_store_output_metadata` + Changed the default value for `--remote_build_event_upload` to `minimal`. + `--experimental_remote_cache_compression` has been renamed to `--remote_cache_compression` + Added a new `max_compatibility_level` attribute to the `bazel_dep` directive, which allows version selection to upgrade a dependency up to the specified compatibility level. + `--experimental_remote_grpc_log` has been renamed to `--remote_grpc_log` + `--incompatible_remote_build_event_upload_respect_no_cache` is now a no-op. + json.decode now takes an optional `default` positional parameter; if this parameter is specified and decoding fails, json.decode will return the `default` value instead of failing Starlark evaluation. + --experimental_repository_disable_download is now promoted to stable and is also available under the name --repository_disable_download . + `applicable_licenses` is no longer allowed on the `platform` rule. Additionally, `default_package_metadata` from any `package` rule will not be applied. + **[Incompatible]** Duplicates inConfiguration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.