Bazel 6.0.0rc3 is now available for those that want to try it out.
You can download it from:https://releases.bazel.build/6.0.0/rc3/index.html
Please report regressions to https://github.com/bazelbuild/bazel/issues
as soon as possible.
The release notes for version 6.0.0 are:
# Release 6.0.0rc3 (2022-11-30)
Add required `--add-opens` server JVM args also with
Also collect clang resource directory with
Make `bazel run` works with minimal mode
Include source files with `cquery --output=files` (#16826)
Fsync before rename after copy in DiskCacheClient
Update GetActionResult for disk cache to check referenced files
Make Java runfiles library compilable with JDK 8
[6.0.0] Default --incompatible_strict_conflict_checks to true.
Revert "[6.0.0] Default --incompatible_strict_conflict_checks to
true. (#16864)" (#16872)
Make C++ runfiles library build with `-Werror=shadow`
Keep credentials cached across build commands.
[6.0.0] Only inject metadata for outputs that cannot be
reconstructed by skyf… (#16879)
Update java_tools v11.9
replace _get_canonical_form(label) with str(label)
there is no cursor control.
to true. See
- `cquery --output=files` also outputs source files.
- `--incompatible_strict_conflict_checks` is flipped to true. See https://github.com/bazelbuild/bazel/issues/16729
- 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).
Work towards #16124
- 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
This release contains contributions from many people at Google, as well as Fabian Meumertzheim, Krzysztof Naglik, UebelAndre, Xùdōng Yáng, Yannic, kshyanashree.