The Bazel team is happy to announce a new version of Bazel, Bazel 0.26.
--incompatible_windows_escape_jvm_flagsis enabled by default, and removed.
--incompatible_windows_style_arg_escapingis enabled by default.
--incompatible_no_output_attr_defaultis enabled by default.
--incompatible_depset_unionis enabled by default.
--Incompatible_disallow_rule_execution_platform_constraints_allowed: When enabled, disallows the use of the
execution_platform_constraints_allowedattribute when defining new rules.
--incompatible_disable_objc_provider_resourcesis now enabled by default.
--tvos_cpusare now additive. This means that you can now split the
--incompatible_objc_framework_cleanupto control whether to enable some objc framework cleanup that changes the API. Specifically, the cleanup changes the objc provider API pertaining to frameworks. This change is expected to be transparent to most users unless they write their own Starlark rules to handle frameworks. See https://github.com/bazelbuild/bazel/issues/7594 for details.
objc_librarydoes not support resource attributes any more. Please read #7594 for more info.
Android resource conflicts will no longer be reported between a strong attr resource and a weak attr resource, if the weak attr does not have format specified.
Added support for compiling against fully qualified
Bazel C++ compile/link Starlark API. Can be used with experimental flag
C++ Starlark API for compilation and linking is no longer whitelisted
--incompatible_make_thinlto_command_lines_standalonehas been added. See #6791 for details.
disable_whole_archive_for_static_libhas been added to allow turning off
legacy_whole_archivefor individual targets. #7362
- Fixed an issue where some
py_runtimeswere incompatible with using
--incompatible_no_kwargs_in_build_filesis added. It fixes a bug where the
**kwargnotation was allowed in
--incompatible_static_name_resolution_in_build_filesis added. This fixes a bug where invalid code was silently accepted.
struct.to_proto()can now convert dictionaries into proto3 text message.
globfunction has a new argument
allow_empty. When set to
False(this will be the default in the future), the glob fails when it doesn't match anything. Please explicitly set
allow_empty = Trueto the globs that need it.
- Windows, Python: the new
falseby default) builds
py_testtargets with correct command line argument escaping. Similar to #7486 but for
Generated Go protobufs now depend on
--incompatible_remove_binary_profileto disable the old binary profiles. Instead use the JSON profile format: https://docs.bazel.build/versions/0.26.0/skylark/performance.html#json-profile
--execution_log_json_filethat output a stable sorted execution log. They will offer a stable replacement to
New platform_mappings ability to allow gradual flag to platforms/toolchains migration. See also #6426
--tls_enabledflag is deprecated. Please provide
grpcsas a scheme in the URLs if TLS should be used for a remote connection.
Alex Eagle gave a talk at ng-conf: The Bazel Opt-in Preview is Here!
The latest release of rules_haskell includes many new improvements, including an initial Windows support.
The latest Buildifier release includes Windows binaries, as well as a JSON output for diagnostics.
A new release of the Visual Studio Code plugin for Bazel was released.
Natan Silnitsky gave the talk How to successfully migrate to Bazel from Maven or Gradle at the Java Eastern Europe Conference.
This release contains contributions from many people at Google, as well as Benjamin Peterson, Brian Topping, clyang82, Dave Lee, George Gensure, Greg, Guro Bokum, Keith Smiley, Max Vorobev, Michael Hackner, Robert Brown, Robert Sayre, Ryan Beasley, and Yannic.