|
| 1 | +## Release 0.23.0 (2019-02-26) |
| 2 | + |
| 3 | +``` |
| 4 | +Baseline: 441fd75d0047f8a998d784c557736ab9075db893 |
| 5 | +
|
| 6 | +Cherry picks: |
| 7 | +
|
| 8 | + + 6ca7763669728253606578a56a205bca3ea883e9: |
| 9 | + Fix a typo |
| 10 | + + 2310b1c2c8b2f32db238f667747e7d5672480f4a: |
| 11 | + Ignore SIGCHLD in test setup script |
| 12 | + + f9eb1b56706f91063e9d080b850fa56964e77324: |
| 13 | + Complete channel initialization in the event loop |
| 14 | +``` |
| 15 | + |
| 16 | +Incompatible changes: |
| 17 | + |
| 18 | + - //src:bazel uses the minimal embedded JDK, if you want to |
| 19 | + avoid the extra steps of minimizing the JDK, use //src:bazel-dev |
| 20 | + instead. |
| 21 | + - //src:bazel uses the minimal embedded JDK, if you want to |
| 22 | + avoid the extra steps of building bazel with the minimized JDK, |
| 23 | + use //src:bazel-dev |
| 24 | + instead. |
| 25 | + - The default value of --host_platform and --platforms will be |
| 26 | + changed to not be dependent on the configuration. This means |
| 27 | + that setting |
| 28 | + --cpu or --host_cpu will not affect the target or host platform. |
| 29 | + - Toolchain resolution for cc rules is now enabled via an |
| 30 | + incompatible flag, --incompatible_enable_cc_toolchain_resolution. |
| 31 | + The previous |
| 32 | + flag, --enabled_toolchain_types, is deprecated and will be |
| 33 | + removed. |
| 34 | + - java_(mutable_|)proto_library: removed strict_deps attribute. |
| 35 | + - Python rules will soon reject the legacy "py" struct provider |
| 36 | + (preview by enabling --incompatible_disallow_legacy_py_provider). |
| 37 | + Upgrade rules to use PyInfo instead. See |
| 38 | + [#7298](https://github.com/bazelbuild/bazel/issues/7298). |
| 39 | + - java_(mutable_|)proto_library: removed strict_deps attribute. |
| 40 | + - Two changes to native Python rules: 1) `default_python_version` |
| 41 | + and `--force_python` are deprecated; use `python_version` and |
| 42 | + `--python_version` respectively instead. You can preview the |
| 43 | + removal of the deprecated names with |
| 44 | + --incompatible_remove_old_python_version_api. See |
| 45 | + [#7308](https://github.com/bazelbuild/bazel/issues/7308). 2) The |
| 46 | + version flag will no longer override the declared version of a |
| 47 | + `py_binary` or `py_test` target. You can preview this new |
| 48 | + behavior with --incompatible_allow_python_version_transitions. |
| 49 | + See [#7307](https://github.com/bazelbuild/bazel/issues/7307). |
| 50 | + |
| 51 | +Important changes: |
| 52 | + |
| 53 | + - There is a new flag available |
| 54 | + `--experimental_java_common_create_provider_enabled_packages` |
| 55 | + that acts as a whitelist for usages of |
| 56 | + `java_common.create_provider`. The constructor will be deprecated |
| 57 | + in Bazel 0.23. |
| 58 | + - [#7024] Allow chaining of the same function type in aquery. |
| 59 | + - Introduces --local_{ram,cpu}_resources, which will take the place |
| 60 | + of --local_resources. |
| 61 | + - [#6930] Add documentation for the aquery command. |
| 62 | + - Incompatible flag `--incompatible_dont_emit_static_libgcc` has |
| 63 | + been flipped (https://github.com/bazelbuild/bazel/issues/6825) |
| 64 | + - Incompatible flag `--incompatible_linkopts_in_user_link_flags` |
| 65 | + has been flipped (https://github.com/bazelbuild/bazel/issues/6826) |
| 66 | + - Flag --incompatible_range_type is removed. |
| 67 | + - Flag --incompatible_disallow_slash_operator is removed. |
| 68 | + - Flag --incompatible_disallow_conflicting_providers is removed. |
| 69 | + - `--incompatible_disallow_data_transition` is now enabled by |
| 70 | + default |
| 71 | + - Allow inclusion of param files in aquery output |
| 72 | + - [#6985] Add test to verify aquery's behavior for Cpp action |
| 73 | + templates. |
| 74 | + - --incompatible_require_feature_configuration_for_pic was flipped |
| 75 | + (https://github.com/bazelbuild/bazel/issues/7007). |
| 76 | + - Also ignore module-info.class in multi-version Jars |
| 77 | + - objc_framework has been deleted. Please refer to |
| 78 | + apple_dynamic_framework_import and apple_static_framework_import |
| 79 | + rules available in |
| 80 | + [rules_apple](https://github.com/bazelbuild/rules_apple/blob/maste |
| 81 | + r/doc/rules-general.md) |
| 82 | + - --test_sharding_strategy=experimental_heuristic is no more |
| 83 | + - objc_bundle_library has been removed. Please migrate to |
| 84 | + rules_apple's |
| 85 | + [apple_resource_bundle](https://github.com/bazelbuild/rules_apple/ |
| 86 | + blob/master/doc/rules-resources.md#apple_resource_bundle). |
| 87 | + - You can now use the attribute `aapt_version` or the flag |
| 88 | + `--android_aapt` to pick the aapt version for android_local_test |
| 89 | + tests |
| 90 | + - In --keep_going mode, Bazel now correctly returns a non-zero exit |
| 91 | + code when encountering a package loading error during target |
| 92 | + pattern parsing of patterns like "//foo:all" and "//foo/...". |
| 93 | + - The default value for --incompatible_strict_action_env has been |
| 94 | + flipped to 'false' again, as we discovered breakages for local |
| 95 | + execution users. We'll need some more time to figure out the best |
| 96 | + way to make this work for local and remote execution. Follow |
| 97 | + https://github.com/bazelbuild/bazel/issues/7026 for more details. |
| 98 | + - Locally-executed spawns tagged "no-cache" no longer upload their |
| 99 | + outputs to the remote cache. |
| 100 | + - Introduces --host_compiler flag to allow setting a compiler for |
| 101 | + host compilation when --host_crosstool_top is specified. |
| 102 | + - --incompatible_expand_directories is enabled by default |
| 103 | + - [aquery] Handle the case of aspect-on-aspect. |
| 104 | + - Fixed a longstanding bug in the http remote cache where the value |
| 105 | + passed to |
| 106 | + --remote_timeout would be interpreted as milliseconds instead of |
| 107 | + seconds. |
| 108 | + - Enable --incompatible_use_jdk10_as_host_javabase by default, see |
| 109 | + https://github.com/bazelbuild/bazel/issues/6661 |
| 110 | + - Add --incompatible_use_jdk11_as_host_javabase: makes JDK 11 the |
| 111 | + default --host_javabase for remote jdk |
| 112 | + (https://github.com/bazelbuild/bazel/issues/7219) |
| 113 | + - Highlight TreeArtifact in aquery text output. |
| 114 | + - Locally-executed spawns tagged "no-cache" no longer upload their |
| 115 | + outputs to the remote cache. |
| 116 | + - java_common APIs now accept JavaToolchainInfo and JavaRuntimeInfo |
| 117 | + instead of configured targets for java_toolchain and java_runtime |
| 118 | + - cc_common.create_cc_toolchain_config_info is stable and available |
| 119 | + for production use |
| 120 | + - incompatible_use_toolchain_providers_in_java_common: pass |
| 121 | + JavaToolchainInfo and JavaRuntimeInfo providers to java_common |
| 122 | + APIs instead of configured targets |
| 123 | + (https://github.com/bazelbuild/bazel/issues/7186) |
| 124 | + - --incompatible_strict_argument_ordering is enabled by default. |
| 125 | + - Bazel now supports reading cache hits from a repository cache, |
| 126 | + even if it doesn't have write access to the cache. |
| 127 | + - Adding arm64e to OSX CROSSTOOL. |
| 128 | + - Ignore package-level licenses on config_setting. |
| 129 | + - Add an optional output_source_jar parameter to java_common.compile |
| 130 | + - --incompatible_disable_objc_provider_resources is now enabled by |
| 131 | + default. This disables ObjcProvider's fields related to resource |
| 132 | + processing. |
| 133 | + - Explicitly set https.protocols and exclude TLSv1.3. |
| 134 | + - Bazel now validates that JAVA_HOME points to a valid JDK and |
| 135 | + falls back to auto-detection by looking up the path of `javac`. |
| 136 | + - Upgrade the embedded JDK version to 11.0.2. |
| 137 | + - Added --incompatible_disable_crosstool_file |
| 138 | + (https://github.com/bazelbuild/bazel/issues/7320) |
| 139 | + - --incompatible_disable_objc_provider_resources is now enabled by |
| 140 | + default. This disables ObjcProvider's fields related to resource |
| 141 | + processing. |
| 142 | + - --incompatible_disable_tools_defaults_package has been flipped. |
| 143 | + - For tests that do not generate a test.xml, Bazel now uses a |
| 144 | + separate action to generate one; this results in minor |
| 145 | + differences in the generated test.xml, and makes the generation |
| 146 | + more reliable overall. |
| 147 | + - incompatible_generate_javacommon_source_jar: java_common.compile |
| 148 | + now always generates a source jar, see |
| 149 | + https://github.com/bazelbuild/bazel/issues/5824. |
| 150 | + - New incompatible flag |
| 151 | + --incompatible_disallow_struct_provider_syntax removes the |
| 152 | + ability for rule implementation functions to return struct. Such |
| 153 | + functions should return a list of providers instead. Migration |
| 154 | + tracking: https://github.com/bazelbuild/bazel/issues/7347 |
| 155 | + |
| 156 | +This release contains contributions from many people at Google, as well as Benjamin Peterson, Ed Schouten, erenon, George Gensure, Greg Estren, Igal Tabachnik, Ittai Zeidman, Jannis Andrija Schnitzer, John Millikin, Keith Smiley, Kelly Campbell, Max Vorobev, nicolov, Robin Nabel. |
| 157 | + |
1 | 158 | ## Release 0.22.0 (2019-01-28) |
2 | 159 |
|
3 | 160 | ``` |
|
0 commit comments