Skip to content

Commit 2f038e8

Browse files
Bazel Release Systemfweikert
Bazel Release System
authored andcommitted
Release 7.0.0-pre.20230412.2 (2023-04-18)
Baseline: 5ab5d80 Cherry picks: + 0d98bf5: Automated rollback of commit 4a2e51b. Incompatible changes: - 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 ``` - Bazel no longer increases the delay between progress updates when there is no cursor control. - 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 --experimental_async_execution flag is now a no-op. - --experimental_replay_action_out_err is not a no-op. - `cquery --output=files` also outputs source files. - `--incompatible_strict_conflict_checks` is flipped to true. See bazelbuild#16729 for details. - `--incompatible_strict_conflict_checks` is flipped to true. See bazelbuild#16729 for details. - `--incompatible_always_include_files_in_data` is flipped to true. See bazelbuild#16654 for details. - This changes the behavior of Python version in exec/host configuration. Mitigation is to set Python version on the targets. - When multiple --deleted_packages options are passed on the command line, they will be concatenated instead of the latest one taking effect. - This has the side effect of changing the message on unsuccessful builds from - JSON profile: Use doubles instead of strings for counter series. - query --output=proto --order_output=deps now returns targets in topological order (previously there was no ordering). - --experimental_build_transitive_python_runfiles is flipped to false. See bazelbuild#16303 for details - --incompatible_python_disable_py2 is flipped to true. See bazelbuild#17293 for details. - When remote cache evicts blobs, Bazel will exit with code 39. - `--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`) - `--incompatible_strict_conflict_checks` is flipped to true. See bazelbuild#16729 for details. - Bazel's local CPU resource on Linux is now container aware. Use `--local_cpu_resources`, `--loading_phase_threads` or `--jobs` to override. - `copy_from_rule` is exec_groups is deprecated (bazelbuild#17668). - --legacy_bazel_java_test is now a no-op - --legacy_bazel_java_test is now a no-op - --legacy_bazel_java_test is now a no-op - `--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 - Remove high priority workers functionality from blaze. New features: - The `aquery` and `cquery` commands now respect the `--query_file` flag just like the `query` command. Important changes: - 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). - Starlark `print()` statements are now emitted iff the line of code is executed. They are no longer replayed on subsequent invocations unless the Starlark code is re-executed. Additionally, multiple identical `print()` statements (same string from the same line of code, e.g. from a loop) are all emitted and no longer deduplicated. - Fixes a bug where some compilation flags would not be applied to a cc_test - removed outdated ctx.host_fragments - removed outdated ctx.host_configuration - Now that the host configuration is finished, `genrule` should prefer the use of `tools` and stop using `exec_tools`. - Added a `native.package_relative_label()` function, which converts a label string to a Label object in the context of the calling package, in contrast to `Label()`, which does so in the context of the current .bzl file. Both functions now also accept relative labels such as `:foo`, and are idempotent. - Update Android manifest merger to v30.1.3, and also drop support for legacy (pre-D8) desugaring. - Adds coverage metric support to android_local_test - Correctly encode double value positive infinity as "inf" instead of "+inf" for textprotos. - Add --use_target_platform_for_tests which uses the target platform for executing tests instead of the execution platform. - 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" - Fixed an issue where WORKSPACE and WORKSPACE-loaded .bzl files couldn't see the Bzlmod root module's mappings when Bzlmod is enabled. - 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. - cc_shared_library is no longer experimental, see bazelbuild#16709 for details - The flag `--distinct_host_configuration` is removed. It has been a no-op since Bazel 6.0.0. - Added `native.module_name()` and `native.module_version()` to allow BUILD macro authors to acquire information about which Bazel module the current repo is associated with. - Add `--skip_incompatible_explicit_targets` option - Remove 'darwin' as a CPU value, use 'darwin_x86_64' instead - cc_test can now be configured by using a native.toolchain(). - `@foo` labels can now be used on the command line as the top-level target (that is, `bazel build @foo` now works). Double-dot syntax is now forbidden (`bazel build ../foo` will no longer work). - 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` - [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`. This release contains contributions from many people at Google, as well as Adam Lavin, Alessandro Patti, Alex Eagle, Amanda L Martin, Andreas Herrmann, Andy Hamon, Ankush Goyal, Anthony Ter-Saakov, Artem Zinnatullin, aryeh, Austin Schuh, Benjamin Lee, Benjamin Peterson, Benjamin Peterson, Benjamin Sigonneau, Ben Lee, Brentley Jones, Chirag Ramani, Christopher Peterson Sauer, Christopher Sauer, Daniel Grunwald, Daniel KT, Daniel Wagner-Hall, Ed Schouten, Emil Kattainen, Ezekiel Warren, Fabian Meumertzheim, Fabian Meumertzheim, Fahrzin Hemmati, Fahrzin Hemmati, Gaspare Vitta, Greg Magolan, Halil Sener, Hao Yuan, hvadehra, hvd, Jack Dai, James Ma, John Hinnegan, Jon Landis, Jon Parise, jonrose-dev, Julio Merino, keertk, Keith Smiley, Konstantin Erman, Krzysztof Naglik, kshyanashree, Kun-Lu, Lee Mracek, lripoche, Malte Poll, Marc Zych, Matt Mackay, Maxwell Elliott, mohamadk, nathyong, Nick Korostelev, Oliver Lee, Patrick Balestra, Patrick Balestra, Philipp Schrader, Red Daly, redwrasse, robincaloudis, Robin Tweedie, Roger Hu, Sagar Pathare, Saleem Abdulrasool, Sara Adams, Sascha Moecker, Severin Strobl, Siddhesh Bhupendra Kuakde, Simon Mavi Stewart, something_vague, Son Luong Ngoc, Stiopa Koltsov, tbaing, Ted Kaplan, Ted Kaplan, Thulio Ferraz Assis, Tom Cnops, Ulf Adams, Ulf Adams, Ulrik Falklof, Uri Baghin, Xavier Bonaventura, Xdng Yng, Xiangquan Xiao, Yannic Bonenberger, Yannic, Yi Cheng, yuzhy8701.
1 parent 274f43a commit 2f038e8

File tree

1 file changed

+180
-0
lines changed

1 file changed

+180
-0
lines changed

CHANGELOG.md

Lines changed: 180 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,183 @@
1+
## Release 7.0.0-pre.20230412.2 (2023-04-18)
2+
3+
```
4+
Baseline: 5ab5d80e08bd42b056403c12f2d1f7be4996e3d4
5+
6+
Cherry picks:
7+
8+
+ 0d98bf5197732fe7a467f52b4317da70cbb58542:
9+
Automated rollback of commit
10+
4a2e51b3d7b7a27d243e8cc233d60fbbaeeb6190.
11+
```
12+
13+
Incompatible changes:
14+
15+
- This has the side effect of changing the message on unsuccessful
16+
builds from
17+
```
18+
FAILED: Build did NOT complete successfully (0 packages loaded)
19+
```
20+
to
21+
```
22+
ERROR: Build did NOT complete successfully
23+
```
24+
- Bazel no longer increases the delay between progress updates when
25+
there is no cursor control.
26+
- This has the side effect of changing the message on unsuccessful
27+
builds from
28+
```
29+
FAILED: Build did NOT complete successfully (0 packages loaded)
30+
```
31+
to
32+
```
33+
ERROR: Build did NOT complete successfully
34+
```
35+
- the --experimental_async_execution flag is now a no-op.
36+
- --experimental_replay_action_out_err is not a no-op.
37+
- `cquery --output=files` also outputs source files.
38+
- `--incompatible_strict_conflict_checks` is flipped to true. See
39+
https://github.com/bazelbuild/bazel/issues/16729 for details.
40+
- `--incompatible_strict_conflict_checks` is flipped to true. See
41+
https://github.com/bazelbuild/bazel/issues/16729 for details.
42+
- `--incompatible_always_include_files_in_data` is flipped to true.
43+
See https://github.com/bazelbuild/bazel/issues/16654 for details.
44+
- This changes the behavior of Python version in exec/host
45+
configuration. Mitigation is to set Python version on the targets.
46+
- When multiple --deleted_packages options are passed on the
47+
command line, they will be concatenated instead of the latest one
48+
taking effect.
49+
- This has the side effect of changing the message on unsuccessful
50+
builds from
51+
- JSON profile: Use doubles instead of strings for counter series.
52+
- query --output=proto --order_output=deps now returns targets in
53+
topological order (previously there was no ordering).
54+
- --experimental_build_transitive_python_runfiles is flipped to
55+
false. See #16303 for details
56+
- --incompatible_python_disable_py2 is flipped to true. See #17293
57+
for details.
58+
- When remote cache evicts blobs, Bazel will exit with code 39.
59+
- `--features` only applies to targets built in the target
60+
configuration, and `--host_features` is used for the host / exec
61+
configuration (gated behind `--incompatible_use_host_features`)
62+
- `--incompatible_strict_conflict_checks` is flipped to true. See
63+
https://github.com/bazelbuild/bazel/issues/16729 for details.
64+
- Bazel's local CPU resource on Linux is now container aware. Use
65+
`--local_cpu_resources`, `--loading_phase_threads` or `--jobs` to
66+
override.
67+
- `copy_from_rule` is exec_groups is deprecated
68+
(https://github.com/bazelbuild/bazel/issues/17668).
69+
- --legacy_bazel_java_test is now a no-op
70+
- --legacy_bazel_java_test is now a no-op
71+
- --legacy_bazel_java_test is now a no-op
72+
- `--experimental_execution_graph_log` no longer exists. Current
73+
users that want local logs need to pass
74+
`--experimental_enable_execution_graph_log
75+
--experimental_execution_graph_log_path=/some/local/path`.
76+
Current users that want logs uploaded to BEP need to pass
77+
`--experimental_enable_execution_graph_log
78+
--experimental_stream_log_file_uploads`.
79+
- Remove 'darwin' as a CPU value, use 'darwin_x86_64' instead
80+
- Remove high priority workers functionality from blaze.
81+
82+
New features:
83+
84+
- The `aquery` and `cquery` commands now respect the
85+
`--query_file` flag just like the `query` command.
86+
87+
Important changes:
88+
89+
- The new path variable `$(rlocationpath ...)` and its plural form
90+
`$(rlocationpaths ...)` can be used to expand labels to the paths
91+
accepted by the `Rlocation` function of runfiles libraries. This
92+
is the preferred way to access data dependencies at runtime and
93+
works on all platforms, even when runfiles are not enabled (e.g.,
94+
on Windows by default).
95+
- Starlark `print()` statements are now emitted iff the line of
96+
code is executed. They are no longer replayed on subsequent
97+
invocations unless the Starlark code is re-executed.
98+
Additionally, multiple identical `print()` statements (same
99+
string from the same line of code, e.g. from a loop) are all
100+
emitted and no longer deduplicated.
101+
- Fixes a bug where some compilation flags would not be applied to
102+
a cc_test
103+
- removed outdated ctx.host_fragments
104+
- removed outdated ctx.host_configuration
105+
- Now that the host configuration is finished, `genrule` should
106+
prefer the use of `tools` and stop using `exec_tools`.
107+
- Added a `native.package_relative_label()` function, which
108+
converts a label string to a Label object in the context of the
109+
calling package, in contrast to `Label()`, which does so in the
110+
context of the current .bzl file. Both functions now also accept
111+
relative labels such as `:foo`, and are idempotent.
112+
- Update Android manifest merger to v30.1.3, and also drop support
113+
for legacy (pre-D8) desugaring.
114+
- Adds coverage metric support to android_local_test
115+
- Correctly encode double value positive infinity as "inf" instead
116+
of "+inf" for textprotos.
117+
- Add --use_target_platform_for_tests which uses the target
118+
platform for executing tests instead of the execution platform.
119+
- Custom C++ rules on Windows calling
120+
cc_common.create_linking_context_from_compilation_outputs should
121+
review whether each target of the rule type should produce a
122+
dynamic library since a condition which blocked their creation
123+
has been moved to the rules from behind the API.
124+
- Add flag `--experimental_remote_cache_ttl` and set the default
125+
value to 3 hours.
126+
- making --incompatible_use_platforms_repo_for_constraints do
127+
nothing. Using constraints from @bazel_tools//platforms with or
128+
without the flag will throw error with message "Constraints from
129+
@bazel_tools//platforms have been removed. Please use constraints
130+
from @platforms repository embedded in Bazel, or preferably
131+
declare dependency on https://github.com/bazelbuild/platforms"
132+
- Fixed an issue where WORKSPACE and WORKSPACE-loaded .bzl files
133+
couldn't see the Bzlmod root module's mappings when Bzlmod is
134+
enabled.
135+
- Subsequent settings of --extra_execution_platforms now override
136+
previous settings, instead of adding them to a list. If you
137+
currently set --extra_execution_platforms more than once, please
138+
migrate by passing a list of values to
139+
--extra_execution_platforms instead so that earlier values aren't
140+
overwritten.
141+
- @bazel_tools//config:common_settings.bzl has been removed.
142+
Use @bazel_skylib//rules:common_settings.bzl instead.
143+
- cc_shared_library is no longer experimental, see
144+
https://github.com/bazelbuild/bazel/issues/16709 for details
145+
- The flag `--distinct_host_configuration` is removed. It has been
146+
a no-op since Bazel 6.0.0.
147+
- Added `native.module_name()` and `native.module_version()` to
148+
allow BUILD macro authors to acquire information about which
149+
Bazel module the current repo is associated with.
150+
- Add `--skip_incompatible_explicit_targets` option
151+
- Remove 'darwin' as a CPU value, use 'darwin_x86_64' instead
152+
- cc_test can now be configured by using a native.toolchain().
153+
- `@foo` labels can now be used on the command line as the
154+
top-level target (that is, `bazel build @foo` now works).
155+
Double-dot syntax is now forbidden (`bazel build ../foo` will no
156+
longer work).
157+
- The location of rules that explicitly specify `generator_name`
158+
and/or `generator_function` attributes (typically because they
159+
are incidentally copied from `native.existing_rule()`) is now the
160+
top-level call in the `BUILD` file, which is consistent with
161+
rules that do not explicitly specify these attributes.
162+
- Warnings (most notably those associated with the `deprecation`
163+
rule attribute) are no longer replayed on subsequent invocations
164+
unless the target in question is re-analyzed. Warnings are purely
165+
informational, so this change has no bearing on the correctness
166+
of the build. Downstream tests that break due to this change
167+
should update their expectations.
168+
- `--experimental_remote_build_event_upload` has been renamed to
169+
`--remote_build_event_upload`
170+
- [Breaking change] platform, constraint_setting, and
171+
constraint_value can no longer take an applicable_licenses value.
172+
Remediation is to remove the attribute and rely on the package
173+
level default.
174+
- `--experimental_action_cache_store_output_metadata` has been
175+
renamed to `--action_cache_store_output_metadata`
176+
- Changed the default value for `--remote_build_event_upload` to
177+
`minimal`.
178+
179+
This release contains contributions from many people at Google, as well as Adam Lavin, Alessandro Patti, Alex Eagle, Amanda L Martin, Andreas Herrmann, Andy Hamon, Ankush Goyal, Anthony Ter-Saakov, Artem Zinnatullin, aryeh, Austin Schuh, Benjamin Lee, Benjamin Peterson, Benjamin Peterson, Benjamin Sigonneau, Ben Lee, Brentley Jones, Chirag Ramani, Christopher Peterson Sauer, Christopher Sauer, Daniel Grunwald, Daniel KT, Daniel Wagner-Hall, Ed Schouten, Emil Kattainen, Ezekiel Warren, Fabian Meumertzheim, Fabian Meumertzheim, Fahrzin Hemmati, Fahrzin Hemmati, Gaspare Vitta, Greg Magolan, Halil Sener, Hao Yuan, hvadehra, hvd, Jack Dai, James Ma, John Hinnegan, Jon Landis, Jon Parise, jonrose-dev, Julio Merino, keertk, Keith Smiley, Konstantin Erman, Krzysztof Naglik, kshyanashree, Kun-Lu, Lee Mracek, lripoche, Malte Poll, Marc Zych, Matt Mackay, Maxwell Elliott, mohamadk, nathyong, Nick Korostelev, Oliver Lee, Patrick Balestra, Patrick Balestra, Philipp Schrader, Red Daly, redwrasse, robincaloudis, Robin Tweedie, Roger Hu, Sagar Pathare, Saleem Abdulrasool, Sara Adams, Sascha Moecker, Severin Strobl, Siddhesh Bhupendra Kuakde, Simon Mavi Stewart, something_vague, Son Luong Ngoc, Stiopa Koltsov, tbaing, Ted Kaplan, Ted Kaplan, Thulio Ferraz Assis, Tom Cnops, Ulf Adams, Ulf Adams, Ulrik Falklof, Uri Baghin, Xavier Bonaventura, Xdng Yng, Xiangquan Xiao, Yannic Bonenberger, Yannic, Yi Cheng, yuzhy8701.
180+
1181
## Release 6.1.2 (2023-04-18)
2182

3183
```

0 commit comments

Comments
 (0)