incompatible_package_group_has_public_syntax #16355

brandjon · 2022-09-29T20:33:42Z

Description: This flag adds the new string constants "public" and "private" as allowed values for package_group's packages attribute. "public" admits every package into the package group, which is the same behavior as "//..." prior to --incompatible_fix_package_group_reporoot_syntax (#16323). "private" admits no packages and has the same effect as omitting it from the list; it is provided merely for symmetry / readability.

Migration: This flag is an incompatible change because, in the output of bazel query --output=proto (or --output=xml), the names "public" and "private" will stringify in a way that's ambiguous with the hypothetical packages //public and //private. To fix this, --incompatible_package_group_includes_double_slash should be enabled whenever this flag is used. There is no separate migration needed just for --incompatible_package_group_has_public_syntax, except that any tooling that statically processes BUILD files or which consumes query output should be prepared for the possibility of the "public" and "private" values.

Note that in .bzl visibility, the values "public" and "private" are always available regardless of this flag.

Rationale: Flipping this change is a prerequisite to #16323 since without "public" there is no replacement for "//...".

The text was updated successfully, but these errors were encountered:

lberki · 2022-10-04T11:20:37Z

To make our discussion on Friday less obscure: why is this planned to be implemented in the packages= attribute as opposed to e.g. two new public= / private= attributes which would be mutually exclusive with each other or packages= or in some other way that doesn't involve making packages= possibly mean two different things?

One of the long-standing and nigh-unfixable issues with the rule-level visibility system is that the visibility= attribute is used for both for things that give rise to dependencies (package group references) and things that don't (//visibility:public and :__pkg__ / :__subpackages) and that makes it interpreting quite ugly.

Whereas it doesn't look like you have the same problem here because you don't ever have dependencies here, heterogenous lists still make me uneasy.

brandjon · 2022-10-05T14:16:50Z

The reason to support these in the packages attribute is to avoid asymmetry between package_group and bzl visibility. Under this approach, the only difference in the kinds of package specifications they accept is that bzl visibility can't tolerate negations.

Having "public"/"private" be valid package specifications for package_group is more of an aesthetic benefit than a practical one. I don't expect people to, e.g., set my_allowlist = ["public"] and then pass it to both visibility() and to a packages attr. But I do like good aesthetics -- it means fewer differences to document and explain.

The reason to have "public"/"private" be package specifications at all, as opposed to special forms of visibility(), is that this lets them compose naturally with other allowlists. I.e., if someone refactors an allowlist between public or private and anything that's in-between, downstream composers of that allowlist are unaffected. Syntactically, it also is a little nicer because it means visibility("public") is just a special case of the syntactic sugar for visibility(["public"]).

If we didn't put "public"/"private" in the packages attr, I probably wouldn't bother implementing public=/private= attrs for package_group.

Actually, I forgot the best reason of all for "public": We already have it in the form of misinterpreting "//...", and I want to fix that in a way that doesn't force people off package_group if possible.

This CL does three things: 1. It adds the special package specifications "public" and "private, guarded behind the flag `--incompatible_package_group_has_public_syntax`. 2. It fixes the behavior of package specification "//..." to mean "all packages in the current repo" rather than "all packages in any repo", guarded behind the flag `--incompatible_fix_package_group_reporoot_syntax`. 3. It fixes the behavior of `bazel query --output=proto` (and `--output=xml`) so that the `packages` attribute is serialized without dropping the leading `//` from package names -- it is now `"//foo/bar/..."` instead of `"foo/bar/..."`. This behavioral change is guarded behind `--incompatible_package_group_includes_double_slash`. The .bzl `visibility()` builtin always acts as if the first two flags are enabled. Work toward #11261. Work toward #16323. Work toward #16355. Work toward #16391. RELNOTES: Added three `package_group`-related flags: `--incompatible_package_group_includes_double_slash` (#16391), `--incompatible_package_group_has_public_syntax` (#16355), and `--incompatible_fix_package_group_reporoot_syntax` (#16323). With these flags, `package_group` can now easily specify "all packages", "no packages", and "all packages in the current repo". In PackageSpecification: - fromString(), fromStringPositive(): rewrote docstring, added bool args for flags, renamed or removed vars for simplicity, added handling of public/private and flag behavior - AllPackagesBeneath(): fixed asStringWithoutRepository() for case of //..., which wasn't likely to arise before. - normalize order of equals(), hashCode(), etc. - AllPackages: change hash, and change str representation to "public" - Add NoPackages, symmetric to AllPackages - NegativePackageSpecification: don't reuse the delegate's hash as our own hash verbatim In PackageGroupTest: - Move `testEverythingSpecificationWorks` to above `testNegativeEverything`, and made it use "public" syntax in place of "//...". - Add test for "private" syntax. - Add test for flag guarding "public"/"private". - Add tests for old and new "//..." behavior. - Add tests that you can't negate "public" or "private". - Add test for illegal combination of flags. - Add assertions for stringification of "public"/"private". Other changes: - Update XmlOutputFormatterTest and ProtoOutputFormatterTest with test cases for the flag. In the latter case, parameterize a helper to allow setting per-test-case flags. - Add test cases to BzlLoadFunctionTest for bzl visibility accepting the list forms `["public"]`/`["private"]`, and for its behavior being unaffected by the new flags. PiperOrigin-RevId: 479347358 Change-Id: I124ca5406bff15615adaa1256e2d7bef69b9d9a5

meteorcloudy · 2022-10-07T09:04:30Z

https://buildkite.com/bazel/bazelisk-plus-incompatible-flags/builds/1291

This flag should be safe to flip (the rules_nodejs failure is unrelated).

meteorcloudy · 2022-10-07T09:05:32Z

To fix this, --incompatible_package_group_includes_double_slash should be enabled whenever this flag is used.

Oh, I see, this flag depends on the other one.

meteorcloudy · 2022-10-11T14:53:32Z

OK, IIUC, flipping this flag would actually fix breakages of #16323, if so, please do so.

This CL does three things: 1. It adds the special package specifications "public" and "private, guarded behind the flag `--incompatible_package_group_has_public_syntax`. 2. It fixes the behavior of package specification "//..." to mean "all packages in the current repo" rather than "all packages in any repo", guarded behind the flag `--incompatible_fix_package_group_reporoot_syntax`. 3. It fixes the behavior of `bazel query --output=proto` (and `--output=xml`) so that the `packages` attribute is serialized without dropping the leading `//` from package names -- it is now `"//foo/bar/..."` instead of `"foo/bar/..."`. This behavioral change is guarded behind `--incompatible_package_group_includes_double_slash`. The .bzl `visibility()` builtin always acts as if the first two flags are enabled. Work toward bazelbuild#11261. Work toward bazelbuild#16323. Work toward bazelbuild#16355. Work toward bazelbuild#16391. RELNOTES: Added three `package_group`-related flags: `--incompatible_package_group_includes_double_slash` (bazelbuild#16391), `--incompatible_package_group_has_public_syntax` (bazelbuild#16355), and `--incompatible_fix_package_group_reporoot_syntax` (bazelbuild#16323). With these flags, `package_group` can now easily specify "all packages", "no packages", and "all packages in the current repo". In PackageSpecification: - fromString(), fromStringPositive(): rewrote docstring, added bool args for flags, renamed or removed vars for simplicity, added handling of public/private and flag behavior - AllPackagesBeneath(): fixed asStringWithoutRepository() for case of //..., which wasn't likely to arise before. - normalize order of equals(), hashCode(), etc. - AllPackages: change hash, and change str representation to "public" - Add NoPackages, symmetric to AllPackages - NegativePackageSpecification: don't reuse the delegate's hash as our own hash verbatim In PackageGroupTest: - Move `testEverythingSpecificationWorks` to above `testNegativeEverything`, and made it use "public" syntax in place of "//...". - Add test for "private" syntax. - Add test for flag guarding "public"/"private". - Add tests for old and new "//..." behavior. - Add tests that you can't negate "public" or "private". - Add test for illegal combination of flags. - Add assertions for stringification of "public"/"private". Other changes: - Update XmlOutputFormatterTest and ProtoOutputFormatterTest with test cases for the flag. In the latter case, parameterize a helper to allow setting per-test-case flags. - Add test cases to BzlLoadFunctionTest for bzl visibility accepting the list forms `["public"]`/`["private"]`, and for its behavior being unaffected by the new flags. PiperOrigin-RevId: 479347358 Change-Id: I124ca5406bff15615adaa1256e2d7bef69b9d9a5

brandjon · 2022-10-12T21:09:44Z

One potential migration issue is that users who have packages = ["//..."] in their package groups, and who want this to mean public, will have to change to packages = ["public"] in sync with their upgrade to use Bazel 6.0. Rewriting to public before upgrading Bazel isn't possible, and upgrading Bazel before rewriting to public means that in the interim the package group will have reduced visibility. Perhaps this reduced visibility isn't a problem if the user doesn't cut a release of their project during that window, since it will still be visible within their local repo.

We could possibly side-step this issue if we cut a 5.x release that flipped this flag, under the justification that this change isn't really incompatible, it just creates a minor ambiguity in an edge case for bazel query output. But we'd still have to release a new 5.x just for the sake of migrating to 6.0, which sounds like overkill.

I'm also a little worried about bootstrapping bazel itself. Building 6.0 with 5.x breaks when I fix the Starlark interpreter's package to be public instead of //.... We could avoid this by allowing the interpreter's visibility to regress in 6.0 and fixing it in a follow-up patch release. We don't really support public use of the Starlark interpreter outside of Copybara and I suppose Stardoc -- and those projects can simply not point to / not vendor in the 6.0 release.

I ran into issues with allowlists in @bazel_tools breaking, but I think I can fix that by splitting a couple BUILD files into BUILD.tools files.

brandjon · 2022-10-12T21:18:32Z

Now that I write that out, it sounds like a reasonable plan: Change the @bazel_tools allowlists to be public and split them into BUILD.tools files to not break bootstrapping of Bazel. Do that atomically with flipping this flag. Run the downstream projects pipeline with a pending change to do that along with flipping the other two incompatible flags. If it passes, submit these changes into 6.0. After 6.0 is released, re-broaden the Starlark interpreter visibility to public.

brandjon · 2022-10-13T16:45:20Z

I ran a downstream test run with all three flags flipped. Test failures would most likely be from --incompatible_fix_package_group_reporoot_syntax, though it's possible we'll see one from --incompatible_package_group_includes_double_slash.

This test run missed an android change for @bazel_tools, so it's possible the android tests would've failed if they hadn't been disabled.

brandjon · 2022-10-13T19:53:50Z

Failures are:

Bazel Remote Cache: CalledProcessError from .bazelci/migration-test.sh, looks like a failure to obtain a Go environment during setup.
TensorFlow: already failing in latest scheduled build
rules_kotlin: couldn't get @io_bazel_rules_kotlin//kotlin while computing main repo mapping. Sounds like an unrelated flake.
rules_python: already failing
rules_rust: //util/import:import_internal_test failed. The log isn't attached, but given that it occurs at execution time and only on one platform, I think it's very unlikely to be related.

So I think that this change and the related changes of #16391 and #16323 are good to go, as far as downstream projects are concerned. Just working on some blockers internal to Bazel..

meteorcloudy · 2022-10-14T08:29:35Z

I can confirm Bazel remote cache, rules_kotlin, rules_rust are flaky failures, so indeed those flags should be good to go!

brandjon · 2022-10-17T14:53:22Z

Planning on submitting flips to these flags' defaults in the Java code tomorrow.

Baseline: 5d0e5a7 Cherry picks: + 512d9b5: Automated rollback of commit 21904a9. + ff927f7: Automated rollback of commit dadc49e. + c5ccb06: Automated rollback of commit bc1e9d8. Incompatible changes: - this incompatible change breaks old instances of http_archive that specified netrc as an absolute path. It is unlikely there are many instances in the wild since the path would refer to a netrc file inside the external repository by absolute path. Migration should be straightforward. - genrule switched to use exec transition instead of host. This can break targets with hardcoded output paths. To avoid using hardcoded paths use make variables, see https://docs.bazel.build/versions/4.2.2/be/make-variables.html#pre defined_label_variables - this incompatible change breaks old instances of http_archive that specified netrc as an absolute path. It is unlikely there are many instances in the wild since... - Error Prone now checks for unused return values of additional methods on `java.lang.Object`, which can be disabled using `--javacopts=-Xep:ReturnValueIgnored:OFF` - Error Prone now checks for unused return values of additional methods on `java.lang.Object`, which can be disabled using `--javacopts=-Xep:ReturnValueIgnored:OFF` - The --incompatible_existing_rules_immutable_view flag has been flipped to true. See #13907 for migration notes. - Split up the C++ archive from the C++ link action and set `CppArchive` as mnemonic. - workspace(managed_directories=) is not available anymore. - --legacy_important_outputs now has a default of false. - --legacy_important_outputs default reverted to true. - objc_library now requires CcInfo in its deps. If this breaks you, add empty CcInfo() to your rule. - Flag --experimental_local_memory_estimate removed. - Added a new flag --incompatible_unambiguous_label_stringification, which causes labels in the main repo to stringify into unambiguous forms starting with an @. See #15916 for more information. - analysis_test moved into testing.analysis_test - Flip incompatible_enable_cc_toolchain_resolution (#7260) - (Rollback) Flip incompatible_enable_cc_toolchain_resolution (#7260) - name parameter is removed from rule call (#16301) - name parameter is removed from rule call (#16301) - name parameter is removed from rule call (#16301) - --incompatible_remote_downloader_send_all_headers is flipped to true. See #16356 for details. Important changes: - Deprecate --incompatible_applicable_licenses flag, in preparation for removal in Bazel 6.x. - Treat py_*.srcs_version="PY2" the same as "PY2ONLY". - The Build Event Protocol now contains file digests and sizes along with the file name and URI. - Refactor system suspend event handling. - alias() can now select() directly on constraint_value() - Allow \a \b \f \v escape sequences in Starlark. - Match remote and local xcode version by most granular version. - Adds `--experimental_worker_multiplex_sandboxing` flag that controls whether to sandbox multiplex workers that support it. - provider() has a new parameter: init, a callback for performing pre-processing and validation of field values. Iff this parameter is set, provider() returns a tuple of 2 elements: the usual provider symbol (which, when called, invokes init) and a raw constructor (which bypasses init). - Tests that fail to create or complete their `TestAttemptContinuation` by throwing an `ExecException` will report an `INCOMPLETE` status. Previously, Bazel would fail to report any status for the test attempt. - Fixed an issue where Bazel could erroneously report a test passes in coverage mode without actually running the test. - Include more information about configurations in cquery proto formatted output. This deprecates the configuration field of AnalysisProtosV2.ConfiguredTarget, and adds a new field, configuration_id, to be used instead. - experimental cc_library.implementation_deps inverted to interface_deps - In aquery and cquery proto output, indicate if a configuration is a tool or non-tool configuration. - Include complete configurations in cquery proto output. - experimental cc_library.implementation_deps inverted to interface_deps - Make protocOpts() publicly accessible. - Add some documentation about how configuration information is conveyed in cquery proto output. - Introduces experimental static library linking API under apple_common.link_multi_arch_static_library - Further deprecation and removal of pkg_tar. Stop supporting legacy use of 'files' attribute, where it could be a list of labels instead of a map of paths to labels. - Removed --incompatible_no_build_defs_pkg flag. It never fulfilled its purpose because --all_incompatible_changes would never set it. The last rule it gated (pkg_tar) is scheduled to be removed in Bazel 6.x. - Add coverage configuration fragment, used to expose output_generator label. - Bazel now no longer includes system headers on macOS in coverage reports (#14969). - android_sdk_repository read $ANDROID_SDK_ROOT in addition to $ANDROID_HOME. - The default dexer is now d8. dx can be optionally enabled using: --define=android_dexmerger_tool=dx_dexmerger \ --define=android_incremental_dexing_tool=dx_dexbuilder \ --define=android_standalone_dexing_tool=dx_compat_dx \ --use_workers_with_dexbuilder - Packaging support for deploy JAR embedded JDK files (hermetic Java). - Don't stamp cc_common.link actions for tool dependencies. - Starlark test rules can use the new inherited_environment parameter of testing.TestEnvironment to specify environment variables whose values should be inherited from the shell environment. - Enable merging permissions during Android manifest merging with the --merge_android_manifest_permissions flag. - Allow specialization to work with constraint_values. - Bazel uses the D8 jar from Maven instead of the SDK. - Make ijar / java_import preserve classes with `@kotlin.Metadata` annotations - Switch cc_test implementation to Starlark. Note: cc_test will now link statically when _targeting_ Windows regardless of host platform (rather than always linking statically when Windows is the _host_). - Switch cc_test implementation to Starlark. Note: cc_test will now link statically when _targeting_ Windows regardless of host platform (rather than always linking statically when Windows is the _host_). - Add devtools/build/lib/worker:work_request_handlers to the remote android tools release package. This will be transitively packaged into all_android_tools. - Bazel uses the D8 jar from Maven instead of the SDK. - android_sdk_repository read $ANDROID_SDK_ROOT in addition to $ANDROID_HOME. - Advance android_tools_pkg version to 0.24.0. - Switch cc_test implementation to Starlark. Note: cc_test will now link statically when _targeting_ Windows regardless of host platform (rather than always linking statically when Windows is the _host_). - Bazel uses the D8 jar from Maven instead of the SDK. - "blaze config" now only reports info from the last build. To compare configurations across multiple builds, redirect "blaze config" output to a file and run your favorite diff tool. - The --incompatible_override_toolchain_transition flag is now always set, and will be removed in the future. Thus, --noincompatible_override_toolchain_transition has no effect, and the value of the incompatible_use_toolchain_transition parameter in aspect() and rule() builtins is ignored. - Switch cc_test implementation to Starlark. Note: cc_test will now link statically when _targeting_ Windows regardless of host platform (rather than always linking statically when Windows is the _host_). - Toolchain types may now be optional, in addition to mandatory. See https://bazel.build/docs/toolchains#optional-toolchains for further details. - Add six to deps of has_services=1 py_proto_librarys. - pkg_tar(symlinks) has been removed. Users needing that feature should migrate to @rules_pkg. - Aspects can now define and use exec groups using the same API as rules. - Removed the obsolete --incompatible_applicable_licenses flag. The feature is permanently enabled. - embedded_tools packages R8 desugarer again - Bazel now selects sh path based on execution platform instead of host platform, making it possible to execute sh actions in multiplatform builds. --shell_executable now only applies to actions configured for host. - labels in genquery.scope are no longer configured. - When Bzlmod is enabled, all Bzlmod-generated repos will have an extra '@' prepended to their names. This effectively enables the canonical label literal syntax for Bzlmod-generated repos (`@@canonicalRepoName//pkg:target`; see https://docs.google.com/document/d/1N81qfCa8oskCk5LqTW-LNthy6EBrDo t7bdUsjz6JFC4/edit?usp=sharing). - Exposed `CcSharedLibraryInfo` to Starlark builtins. - Enable --use_top_level_targets_for_symlinks by default. - Singlejar accepts runtime Created-By field - --noincompatible_disable_managed_directories, and with that, workspace(managed_directories=) is not supported anymore. - Bazel supports D8 desugaring, albeit without persistent workers - Remove mtime options from pkg_tar. Users should migrate to @rules_pkg. - Test for experimental multiplexed persistent resource processor. - Added new register_{execution_platforms,toolchains} directives to the MODULE.bazel file, to replace the {execution_platforms,toolchains}_to_register attributes on the module() directive. - The legacy pkg_tar no longer supports the ability to untar and repackage an input tar file (`deps` attribute). Users needed that capability must switch to github.com/bazelbuild/rules_pkg. - `cquery`'s new output mode [`--output=files`](https://bazel.build/docs/cquery#files-output) lists the output files of the targets matching the query. It takes the current value of `--output_groups` into account. - Change singlejar metadata to report Created-By Bazel - Add support for fetching RPC credentials from credential helper. - Revert interface_deps back to implementation_deps after problem reported in. Use `buildozer 'rename deps implementation_deps' //...:%cc_library; buildozer 'rename interface_deps deps' //...:%cc_library` - Fix for desugaring failure on Bazel+Android+Windows build scenario. - D8 is the default desugarer - Migrate main_dex_list_creator to D8 (DX deprecation) - --experimental_enable_bzlmod has been renamed --enable_bzlmod, and still defaults to false. - selects() no longer produce irrelevant duplicate label checks - Adds a dexer output cache to CompatDexBuilder to improve build speed. - Improved error messages when analyzing inline bzl code - Improved error messages when analyzing inline bzl code - The `@bazel_tools//tools/cpp:compiler` flag now has the value `gcc` if the configured compiler is detected to be gcc rather than the generic value `compiler`. A branch for `gcc` may have to be added to `select` statements that do not have a default case that handles gcc appropriately. - The `get_child` method of `path` now accepts an arbitrary number of relative path strings as positional arguments. - SourceManifestAction supports `Action.content` - Add --incompatible_build_transitive_python_runfiles alias. See #16303 - The @bazel_tools//tools/cpp:compiler flag now has the value `clang` for the auto-configured Xcode toolchain rather than the generic value compiler. A branch for `clang` may have to be added to select statements that do not have a default case that handles this toolchain appropriately. - added additional debug message to warn of skipped toolchains during resolution - The deprecated --remote_allow_symlink_upload flag has been removed. Symlinks in local action outputs are always permitted, even with remote caching. Whether they're uploaded as symlinks or as the files/directories they point to is still determined by the --incompatible_remote_symlinks flag. - Added `struct`, `json`, `proto`, and `depset` to the starlark environment of Bazel's cquery (--output=starlark) command - Added three `package_group`-related flags: `--incompatible_package_group_includes_double_slash` (#16391), `--incompatible_package_group_has_public_syntax` (#16355), and `--incompatible_fix_package_group_reporoot_syntax` (#16323). With these flags, `package_group` can now easily specify "all packages", "no packages", and "all packages in the current repo". This release contains contributions from many people at Google, as well as Adam Azarchs, Adam Wolf, Albert Lloveras, Alessandro Patti, Alex Eagle, Alex Scott, Alex Torok, Andreas Fuchs, Andreas Herrmann, Andrew Katson, Andrew Klotz, Ara Nguyen, arunkumar9t2, arun.sampathkumar, Ast-x64, Benedek Thaler, Benjamin Lee, Benjamin Peterson, Ben Lee, Bohdan Vanieiev, Bo Zhang, Bo Zhang, Bradley Burns, Brandon Duffany, Brandon Jacklyn, Brentley Jones, Brentley Jones, Chad Miller, Charles-Francois Natali, Chris Clearwater, Chris Fredrickson, Christopher Peterson Sauer, Christopher Sauer, ckiffel, Cristian Hancila, crydell-ericsson, Dan Fleming, Daniel Wagner-Hall, Danny Wolf, David Ostrovsky, David Sanderson, Denys Kurylenko, dhmemi, Dimi Shahbaz, divanorama, dmaclach, Ed Schouten, Emil Kattainen, Eric Song, Fabian Brandstetter, Fabian Meumertzheim, floriographygoth, Fredrik Medley, George Prekas, gkgoat1, gkorlam, Greg Estren, Greg, Gregory Fong, Greg Roodt, Grzegorz Lukasik, Halil Sener, Hannes Kufler, homuler, hvadehra, hvd, Igor Nazarenko, James Broadhead, Jan, Jason Tan, Jay Bazuzi, Jeremy Volkman, jheaff1, Jiawen Chen, Joel Williamson, John Laxson, John Millikin, Jonathan Gerrish, Jon Shea, juanchoviedo, Kaiqin Chen, Keith Smiley, Ken Micklas, Kevin Lin, Kiron, Krishna Ersson, kshyanashree, lihu, Luc Bertrand, Luis Fernando Pino Duque, Marek uppa, Matt Clarkson, Matt Mackay, Michael P. Nitowski, Mikhail Balabin, Mostyn Bramley-Moore, Nick Korostelev, Nitesh Anandan, Niyas Sait, Noa Resare, Oscar Bonilla, Patrick Balestra, Paul Tarjan, Peter Mounce, Philipp Schrader, Pras Velagapudi, Rahul Butani, Rajeshwar Reddy T, Rifqi Mulya Fahmi, Roman Salvador, rustberry, Ryan Beasley, Ryan Schmidt, Sahin Yort, Saleem Abdulrasool, Shuai Zhang, Simon Bjorklen, Son Luong Ngoc, Stephan Wolski, Steve Vermeulen, Stiopa Koltsov, Sven Tiffe, Takeo Sawada, Tao Wang, Ted Kaplan, Tetsuo Kiso, Thi Doan, Thomas Chen, ThomasCJY, Thomas, Thomas Zayouna, Timothe Peignier, Tomas Volf, Tom de Goede, Ulf Adams, Ulrik Falklof, vardaro, Vasilios Pantazopoulos, Vladimir Tagakov, William Muir, Xavier Bonaventura, Xdng Yng, Yannic Bonenberger, Yannic Bonenberger, Yannic, Yannic, Yesudeep Mangalapilly, Yuval K, Zhongpeng Lin.

Baseline: e7218d5 Incompatible changes: - In package_group's `packages` attribute, the syntax "//..." now refers to all packages in the same repository as the package group, rather than all packages everywhere. The new item "public" can be used instead to obtain the old behavior. In `bazel query --output=proto` (and `--output=xml`), the `packages` attribute now serializes with the leading double slash included (for instance, `//foo/bar/...` instead of `foo/bar/...`). See also #16355, #16323, and #16391. New features: - Support local_repository in Bazel Registry's source.json file Important changes: - Record hermetic packaged JDK modules file size in deploy JAR manifest 'JDK-Lib-Modules-Size' attribute. - .bzl files may now set a visibility to guard what other .bzl and BUILD files may load them. See [...] for more information. This release contains contributions from many people at Google, as well as Adam Singer, Albert Lloveras, Alex Eagle, Benjamin Lee, Benjamin Peterson, Christopher Rydell, Ed Schouten, Eric Wendelin, Fabian Meumertzheim, Jordan, Keith Smiley, Kirill Zabelin, Son Luong Ngoc, Tetsuo Kiso, Waleed Khan, Xavier Bonaventura, Yannic Bonenberger.

Baseline: d60ce2c Cherry picks: + 490f8ba: kshyanashree is the release manager of 6.0.0 + 4e66d93: Automated rollback of commit 2a28909. + 48a8d01: Allow C/C++ coverage collection for external targets + ec7be34: Temporarily set parent directory of the input to writable if it is not. + b098434: Infer CPUs for tvOS and watchOS when on Apple Silicon + 5cea7dd: Improve the documentation for ctx.actions.symlink. + a82d26f: Add quotes to "Tip" + 75b0f3a: Write a repo mapping manifest in the runfiles directory (#16555) + 07c5c1a: Ensure repository names don't start with `~` + 30f6c82: Escape tilde more gracefully + cf3f48c: Relax `Label` repo visibility validation + 4477823: Use "apparent name" instead of "local name" in Bzlmod docs + 55f4f48: Bazel DevSite: Add required css file. + a706994: Remove logic that increases delay between progress updates over time + 1d514ab: Remove references to io_bazel repository + b0357bd: Relnotes python script + 8f95651: Allow Java coverage collection for external targets + bddb191: Fix race condition in package-bazel.sh + a757852: Decanonicalize labels emitted by {a,c,}query if possible + 9d250ed: Add uniquify parameter to TemplateDict.add_joined + f02bcf8: Fix identical gcov json file name problem + a159330: Add `$(rlocationpath(s) ...)` expansion + 56f54da: Rollup of SBOM correctness fixes (#16655) + 72e6e94: [cc] Add cc toolchain to starlark cc_proto_library (#16661) + 8f28513: Make C++ runfiles library repo mapping aware + 95f9adc: Always collect FileProvider's filesToBuild as data runfiles + 4959d34: fix: export constraints.bzl file from @local_config_platform so it can be used in downstream bzl_library targets + 4919d4a: Add --host_per_file_copt (#16695) + 0a23d46: Moving some tests for `RemoteActionFileSystem` of BwoB to a base class. + 9296068: [remote/downloader] Don't include headers in `FetchBlobRequest` + 128d833: [remote] Respect whether the server supports action cache updates + 38c5019: [remote/downloader] Migrate `Downloader` to take `Credentials` (#16732) + 5929cb7: Stage repository mapping manifest as a root symlink (#16733) + 455454a: Expose current repository name to Java with @AutoBazelRepository + 97dea59: Implement getDirectoryEntries and readdir for RemoteActionFileSystem. + aa45f5f: Move integration tests for BwoB to a base class and add more tests there. + 1b073ac: Make Java runfiles library repo mapping aware + 148bbb1: Use `_repo_mapping` in C++ runfiles library (#16752) + 25558ad: Add --experimental_action_cache_store_output_metadata to the expansio… + 6e945e8: Treat `DEBUG` events as progress-like. + 1940c5d: redact 'token' strings from logging + 0b64525: Make Bash runfiles library repo mapping aware (#16753) + 4caae75: Automated rollback of commit 8f95651. + 13ff6d9: Fix Bash rlocation failure with stricter Bash options + bd88c7e: Make bazel Android remote deps compatible with bzlmod (#16772) + 6f6d4cc: Flip `--incompatible_always_include_files_in_data` + 94355b1: Add required `--add-opens` server JVM args also with non-embedded JDK + 8349c95: Also collect clang resource directory with `-no-canonical-prefixes` + dce6ed7: Make `bazel run` works with minimal mode + ca8674c: Include source files with `cquery --output=files` (#16826) + 9cb5e0a: Fsync before rename after copy in DiskCacheClient + 23ffce5: Update GetActionResult for disk cache to check referenced files when … + 0bc0ff5: Make Java runfiles library compilable with JDK 8 + fe16965: [6.0.0] Default --incompatible_strict_conflict_checks to true. (#16864) + 99ca86f: Revert "[6.0.0] Default --incompatible_strict_conflict_checks to true. (#16864)" (#16872) + 312238f: Make C++ runfiles library build with `-Werror=shadow` + 2baa5a4: Keep credentials cached across build commands. + 8818a57: [6.0.0] Only inject metadata for outputs that cannot be reconstructed by skyf… (#16879) + 31e4bf4: Update java_tools v11.9 + cd40666: replace _get_canonical_form(label) with str(label) + e2bc237: Avoid exceptions from hermetic sandbox for unsupported artifact subclasses + b564d14: Remove warnings about ignored starlark options + 7ccc661: [6.0.0] Emit Tree objects in topological order (#16904) + 86dee6d: Correctly match regex with tree artifact + 14925b5: Always use target's attributes to set Python version (#16959) + a247502: Add 'toolchain' parameter to actions.{run,run_shell} + 497b7e4: Fix Bash `runfiles_current_repository` with RBE + 0a2c4ed: Fix corner cases in Bash runfiles library + 33b514b: Fix runfiles creation with MANIFEST when building without the bytes + 3a13af4: Remove LCOV merger dependency of `cc_test` without coverage (#17004) + 25ba76c: Include full tree artifact in inputs when prefetcher doesn't support partial tree artifacts. Incompatible changes: - this incompatible change breaks old instances of http_archive that specified netrc as an absolute path. It is unlikely there are many instances in the wild since the path would refer to a netrc file inside the external repository by absolute path. Migration should be straightforward. - genrule switched to use exec transition instead of host. This can break targets with hardcoded output paths. To avoid using hardcoded paths use make variables, see https://docs.bazel.build/versions/4.2.2/be/make-variables.html#pre defined_label_variables - this incompatible change breaks old instances of http_archive that specified netrc as an absolute path. It is unlikely there are many instances in the wild since... - Error Prone now checks for unused return values of additional methods on `java.lang.Object`, which can be disabled using `--javacopts=-Xep:ReturnValueIgnored:OFF` - Error Prone now checks for unused return values of additional methods on `java.lang.Object`, which can be disabled using `--javacopts=-Xep:ReturnValueIgnored:OFF` - The --incompatible_existing_rules_immutable_view flag has been flipped to true. See #13907 for migration notes. - Split up the C++ archive from the C++ link action and set `CppArchive` as mnemonic. - workspace(managed_directories=) is not available anymore. - --legacy_important_outputs now has a default of false. - --legacy_important_outputs default reverted to true. - objc_library now requires CcInfo in its deps. If this breaks you, add empty CcInfo() to your rule. - Flag --experimental_local_memory_estimate removed. - Added a new flag --incompatible_unambiguous_label_stringification, which causes labels in the main repo to stringify into unambiguous forms starting with an @. See #15916 for more information. - analysis_test moved into testing.analysis_test - Flip incompatible_enable_cc_toolchain_resolution (#7260) - (Rollback) Flip incompatible_enable_cc_toolchain_resolution (#7260) - name parameter is removed from rule call (#16301) - name parameter is removed from rule call (#16301) - name parameter is removed from rule call (#16301) - --incompatible_remote_downloader_send_all_headers is flipped to true. See #16356 for details. - GrpcRemoteDownloader only includes relevant headers instead of sending all credentials. - In package_group's `packages` attribute, the syntax "//..." now refers to all packages in the same repository as the package group, rather than all packages everywhere. The new item "public" can be used instead to obtain the old behavior. In `bazel query --output=proto` (and `--output=xml`), the `packages` attribute now serializes with the leading double slash included (for instance, `//foo/bar/...` instead of `foo/bar/...`). See also #16355, #16323, and #16391. - Bazel no longer increases the delay between progress updates when there is no cursor control. - `--incompatible_always_include_files_in_data` is flipped to true. See #16654 for details. - `cquery --output=files` also outputs source files. Closes #16602. - `--incompatible_strict_conflict_checks` is flipped to true. See #16729 for details. - This changes the behavior of Python version in exec/host configuration. Mitigation is to set Python version on the targets. New features: - Support local_repository in Bazel Registry's source.json file Important changes: - Deprecate --incompatible_applicable_licenses flag, in preparation for removal in Bazel 6.x. - Treat py_*.srcs_version="PY2" the same as "PY2ONLY". - The Build Event Protocol now contains file digests and sizes along with the file name and URI. - Refactor system suspend event handling. - alias() can now select() directly on constraint_value() - Allow \a \b \f \v escape sequences in Starlark. - Match remote and local xcode version by most granular version. - Adds `--experimental_worker_multiplex_sandboxing` flag that controls whether to sandbox multiplex workers that support it. - provider() has a new parameter: init, a callback for performing pre-processing and validation of field values. Iff this parameter is set, provider() returns a tuple of 2 elements: the usual provider symbol (which, when called, invokes init) and a raw constructor (which bypasses init). - Tests that fail to create or complete their `TestAttemptContinuation` by throwing an `ExecException` will report an `INCOMPLETE` status. Previously, Bazel would fail to report any status for the test attempt. - Fixed an issue where Bazel could erroneously report a test passes in coverage mode without actually running the test. - Include more information about configurations in cquery proto formatted output. This deprecates the configuration field of AnalysisProtosV2.ConfiguredTarget, and adds a new field, configuration_id, to be used instead. - experimental cc_library.implementation_deps inverted to interface_deps - In aquery and cquery proto output, indicate if a configuration is a tool or non-tool configuration. - Include complete configurations in cquery proto output. - experimental cc_library.implementation_deps inverted to interface_deps - Make protocOpts() publicly accessible. - Add some documentation about how configuration information is conveyed in cquery proto output. - Introduces experimental static library linking API under apple_common.link_multi_arch_static_library - Further deprecation and removal of pkg_tar. Stop supporting legacy use of 'files' attribute, where it could be a list of labels instead of a map of paths to labels. - Removed --incompatible_no_build_defs_pkg flag. It never fulfilled its purpose because --all_incompatible_changes would never set it. The last rule it gated (pkg_tar) is scheduled to be removed in Bazel 6.x. - Add coverage configuration fragment, used to expose output_generator label. - Bazel now no longer includes system headers on macOS in coverage reports (#14969). - android_sdk_repository read $ANDROID_SDK_ROOT in addition to $ANDROID_HOME. - The default dexer is now d8. dx can be optionally enabled using: --define=android_dexmerger_tool=dx_dexmerger \ --define=android_incremental_dexing_tool=dx_dexbuilder \ --define=android_standalone_dexing_tool=dx_compat_dx \ --use_workers_with_dexbuilder - Packaging support for deploy JAR embedded JDK files (hermetic Java). - Don't stamp cc_common.link actions for tool dependencies. - Starlark test rules can use the new inherited_environment parameter of testing.TestEnvironment to specify environment variables whose values should be inherited from the shell environment. - Enable merging permissions during Android manifest merging with the --merge_android_manifest_permissions flag. - Allow specialization to work with constraint_values. - Bazel uses the D8 jar from Maven instead of the SDK. - Make ijar / java_import preserve classes with `@kotlin.Metadata` annotations - Switch cc_test implementation to Starlark. Note: cc_test will now link statically when _targeting_ Windows regardless of host platform (rather than always linking statically when Windows is the _host_). - Switch cc_test implementation to Starlark. Note: cc_test will now link statically when _targeting_ Windows regardless of host platform (rather than always linking statically when Windows is the _host_). - Add devtools/build/lib/worker:work_request_handlers to the remote android tools release package. This will be transitively packaged into all_android_tools. - Bazel uses the D8 jar from Maven instead of the SDK. - android_sdk_repository read $ANDROID_SDK_ROOT in addition to $ANDROID_HOME. - Advance android_tools_pkg version to 0.24.0. - Switch cc_test implementation to Starlark. Note: cc_test will now link statically when _targeting_ Windows regardless of host platform (rather than always linking statically when Windows is the _host_). - Bazel uses the D8 jar from Maven instead of the SDK. - "blaze config" now only reports info from the last build. To compare configurations across multiple builds, redirect "blaze config" output to a file and run your favorite diff tool. - The --incompatible_override_toolchain_transition flag is now always set, and will be removed in the future. Thus, --noincompatible_override_toolchain_transition has no effect, and the value of the incompatible_use_toolchain_transition parameter in aspect() and rule() builtins is ignored. - Switch cc_test implementation to Starlark. Note: cc_test will now link statically when _targeting_ Windows regardless of host platform (rather than always linking statically when Windows is the _host_). - Toolchain types may now be optional, in addition to mandatory. See https://bazel.build/docs/toolchains#optional-toolchains for further details. - Add six to deps of has_services=1 py_proto_librarys. - pkg_tar(symlinks) has been removed. Users needing that feature should migrate to @rules_pkg. - Aspects can now define and use exec groups using the same API as rules. - Removed the obsolete --incompatible_applicable_licenses flag. The feature is permanently enabled. - embedded_tools packages R8 desugarer again - Bazel now selects sh path based on execution platform instead of host platform, making it possible to execute sh actions in multiplatform builds. --shell_executable now only applies to actions configured for host. - labels in genquery.scope are no longer configured. - When Bzlmod is enabled, all Bzlmod-generated repos will have an extra '@' prepended to their names. This effectively enables the canonical label literal syntax for Bzlmod-generated repos (`@@canonicalRepoName//pkg:target`; see https://docs.google.com/document/d/1N81qfCa8oskCk5LqTW-LNthy6EBrDo t7bdUsjz6JFC4/edit?usp=sharing). - Exposed `CcSharedLibraryInfo` to Starlark builtins. - Enable --use_top_level_targets_for_symlinks by default. - Singlejar accepts runtime Created-By field - --noincompatible_disable_managed_directories, and with that, workspace(managed_directories=) is not supported anymore. - Bazel supports D8 desugaring, albeit without persistent workers - Remove mtime options from pkg_tar. Users should migrate to @rules_pkg. - Test for experimental multiplexed persistent resource processor. - Added new register_{execution_platforms,toolchains} directives to the MODULE.bazel file, to replace the {execution_platforms,toolchains}_to_register attributes on the module() directive. - The legacy pkg_tar no longer supports the ability to untar and repackage an input tar file (`deps` attribute). Users needed that capability must switch to github.com/bazelbuild/rules_pkg. - `cquery`'s new output mode [`--output=files`](https://bazel.build/docs/cquery#files-output) lists the output files of the targets matching the query. It takes the current value of `--output_groups` into account. - Change singlejar metadata to report Created-By Bazel - Add support for fetching RPC credentials from credential helper. - Revert interface_deps back to implementation_deps after problem reported in. Use `buildozer 'rename deps implementation_deps' //...:%cc_library; buildozer 'rename interface_deps deps' //...:%cc_library` - Fix for desugaring failure on Bazel+Android+Windows build scenario. - D8 is the default desugarer - Migrate main_dex_list_creator to D8 (DX deprecation) - --experimental_enable_bzlmod has been renamed --enable_bzlmod, and still defaults to false. - selects() no longer produce irrelevant duplicate label checks - Adds a dexer output cache to CompatDexBuilder to improve build speed. - Improved error messages when analyzing inline bzl code - Improved error messages when analyzing inline bzl code - The `@bazel_tools//tools/cpp:compiler` flag now has the value `gcc` if the configured compiler is detected to be gcc rather than the generic value `compiler`. A branch for `gcc` may have to be added to `select` statements that do not have a default case that handles gcc appropriately. - The `get_child` method of `path` now accepts an arbitrary number of relative path strings as positional arguments. - SourceManifestAction supports `Action.content` - Add --incompatible_build_transitive_python_runfiles alias. See #16303 - The @bazel_tools//tools/cpp:compiler flag now has the value `clang` for the auto-configured Xcode toolchain rather than the generic value compiler. A branch for `clang` may have to be added to select statements that do not have a default case that handles this toolchain appropriately. - added additional debug message to warn of skipped toolchains during resolution - The deprecated --remote_allow_symlink_upload flag has been removed. Symlinks in local action outputs are always permitted, even with remote caching. Whether they're uploaded as symlinks or as the files/directories they point to is still determined by the --incompatible_remote_symlinks flag. - Added `struct`, `json`, `proto`, and `depset` to the starlark environment of Bazel's cquery (--output=starlark) command - Added three `package_group`-related flags: `--incompatible_package_group_includes_double_slash` (#16391), `--incompatible_package_group_has_public_syntax` (#16355), and `--incompatible_fix_package_group_reporoot_syntax` (#16323). With these flags, `package_group` can now easily specify "all packages", "no packages", and "all packages in the current repo". - Record hermetic packaged JDK modules file size in deploy JAR manifest 'JDK-Lib-Modules-Size' attribute. - .bzl files may now set a visibility to guard what other .bzl and BUILD files may load them. See [...] for more information. - Deletes the --extra_proguard_specs Blaze flag - 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 Fixes #10923 Closes #16428. - 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 This release contains contributions from many people at Google, as well as Adam Azarchs, Adam Singer, Adam Wolf, Albert Lloveras, Alessandro Patti, Alex Eagle, Alex Scott, Alex Torok, Andreas Fuchs, Andreas Herrmann, Andrew Katson, Andrew Klotz, Ara Nguyen, arunkumar9t2, arun.sampathkumar, Ast-x64, Benedek Thaler, Benjamin Lee, Benjamin Peterson, Ben Lee, Bohdan Vanieiev, Bo Zhang, Bo Zhang, Bradley Burns, Brandon Duffany, Brandon Jacklyn, Brentley Jones, Brentley Jones, Chad Miller, Charles-Francois Natali, Chris Clearwater, Chris Fredrickson, Christopher Peterson Sauer, Christopher Rydell, Christopher Sauer, ckiffel, Cristian Hancila, crydell-ericsson, Dan Fleming, Daniel Wagner-Hall, Danny Wolf, David Ostrovsky, David Sanderson, Denys Kurylenko, dhmemi, Dimi Shahbaz, divanorama, dmaclach, Ed Schouten, Emil Kattainen, Eric Song, Eric Wendelin, Fabian Brandstetter, Fabian Meumertzheim, floriographygoth, Fredrik Medley, George Prekas, gkgoat1, gkorlam, Greg Estren, Greg, Gregory Fong, Greg Roodt, Grzegorz Lukasik, Halil Sener, Hannes Kufler, homuler, hvadehra, hvd, Igor Nazarenko, James Broadhead, Jan, Jason Tan, Jay Bazuzi, Jeremy Volkman, jheaff1, Jiawen Chen, Joel Williamson, John Laxson, John Millikin, Jonathan Gerrish, Jon Shea, Jordan, juanchoviedo, Kaiqin Chen, Keith Smiley, Ken Micklas, Kevin Lin, Kirill Zabelin, Kiron, Krishna Ersson, Krzysztof Naglik, kshyanashree, lihu, Luc Bertrand, Luis Fernando Pino Duque, lunch-glide-pepper, Marek uppa, Matt Clarkson, Matt Mackay, Michael P. Nitowski, Mikhail Balabin, Mostyn Bramley-Moore, Nick Korostelev, Nitesh Anandan, Niyas Sait, Noa Resare, Olek Wojnar, Oscar Bonilla, Patrick Balestra, Paul Tarjan, Peter Mounce, Philipp Schrader, Pras Velagapudi, Rahul Butani, Rajeshwar Reddy T, Rifqi Mulya Fahmi, Roman Salvador, rustberry, Ryan Beasley, Ryan Schmidt, Sahin Yort, Saleem Abdulrasool, Sara Adams, Shuai Zhang, Simon Bjorklen, Son Luong Ngoc, Stephan Wolski, Steve Vermeulen, Stiopa Koltsov, Sven Tiffe, Takeo Sawada, Tao Wang, Ted Kaplan, Tetsuo Kiso, Thi Doan, Thomas Chen, ThomasCJY, Thomas, Thomas Zayouna, Timothe Peignier, Tomas Volf, Tom de Goede, UebelAndre, Ulf Adams, Ulrik Falklof, vardaro, Vasilios Pantazopoulos, Vladimir Tagakov, Waleed Khan, William Muir, Xavier Bonaventura, Xdng Yng, Xiangquan Xiao, Xùdōng Yáng, Yannic Bonenberger, Yannic Bonenberger, Yannic, Yannic, Yesudeep Mangalapilly, Yuval K, Zhongpeng Lin.

Baseline: d60ce2c Cherry picks: + 490f8ba: kshyanashree is the release manager of 6.0.0 + 4e66d93: Automated rollback of commit 2a28909. + 48a8d01: Allow C/C++ coverage collection for external targets + ec7be34: Temporarily set parent directory of the input to writable if it is not. + b098434: Infer CPUs for tvOS and watchOS when on Apple Silicon + 5cea7dd: Improve the documentation for ctx.actions.symlink. + a82d26f: Add quotes to "Tip" + 75b0f3a: Write a repo mapping manifest in the runfiles directory (bazelbuild#16555) + 07c5c1a: Ensure repository names don't start with `~` + 30f6c82: Escape tilde more gracefully + cf3f48c: Relax `Label` repo visibility validation + 4477823: Use "apparent name" instead of "local name" in Bzlmod docs + 55f4f48: Bazel DevSite: Add required css file. + a706994: Remove logic that increases delay between progress updates over time + 1d514ab: Remove references to io_bazel repository + b0357bd: Relnotes python script + 8f95651: Allow Java coverage collection for external targets + bddb191: Fix race condition in package-bazel.sh + a757852: Decanonicalize labels emitted by {a,c,}query if possible + 9d250ed: Add uniquify parameter to TemplateDict.add_joined + f02bcf8: Fix identical gcov json file name problem + a159330: Add `$(rlocationpath(s) ...)` expansion + 56f54da: Rollup of SBOM correctness fixes (bazelbuild#16655) + 72e6e94: [cc] Add cc toolchain to starlark cc_proto_library (bazelbuild#16661) + 8f28513: Make C++ runfiles library repo mapping aware + 95f9adc: Always collect FileProvider's filesToBuild as data runfiles + 4959d34: fix: export constraints.bzl file from @local_config_platform so it can be used in downstream bzl_library targets + 4919d4a: Add --host_per_file_copt (bazelbuild#16695) + 0a23d46: Moving some tests for `RemoteActionFileSystem` of BwoB to a base class. + 9296068: [remote/downloader] Don't include headers in `FetchBlobRequest` + 128d833: [remote] Respect whether the server supports action cache updates + 38c5019: [remote/downloader] Migrate `Downloader` to take `Credentials` (bazelbuild#16732) + 5929cb7: Stage repository mapping manifest as a root symlink (bazelbuild#16733) + 455454a: Expose current repository name to Java with @AutoBazelRepository + 97dea59: Implement getDirectoryEntries and readdir for RemoteActionFileSystem. + aa45f5f: Move integration tests for BwoB to a base class and add more tests there. + 1b073ac: Make Java runfiles library repo mapping aware + 148bbb1: Use `_repo_mapping` in C++ runfiles library (bazelbuild#16752) + 25558ad: Add --experimental_action_cache_store_output_metadata to the expansio… + 6e945e8: Treat `DEBUG` events as progress-like. + 1940c5d: redact 'token' strings from logging + 0b64525: Make Bash runfiles library repo mapping aware (bazelbuild#16753) + 4caae75: Automated rollback of commit 8f95651. + 13ff6d9: Fix Bash rlocation failure with stricter Bash options + bd88c7e: Make bazel Android remote deps compatible with bzlmod (bazelbuild#16772) + 6f6d4cc: Flip `--incompatible_always_include_files_in_data` + 94355b1: Add required `--add-opens` server JVM args also with non-embedded JDK + 8349c95: Also collect clang resource directory with `-no-canonical-prefixes` + dce6ed7: Make `bazel run` works with minimal mode + ca8674c: Include source files with `cquery --output=files` (bazelbuild#16826) + 9cb5e0a: Fsync before rename after copy in DiskCacheClient + 23ffce5: Update GetActionResult for disk cache to check referenced files when … + 0bc0ff5: Make Java runfiles library compilable with JDK 8 + fe16965: [6.0.0] Default --incompatible_strict_conflict_checks to true. (bazelbuild#16864) + 99ca86f: Revert "[6.0.0] Default --incompatible_strict_conflict_checks to true. (bazelbuild#16864)" (bazelbuild#16872) + 312238f: Make C++ runfiles library build with `-Werror=shadow` + 2baa5a4: Keep credentials cached across build commands. + 8818a57: [6.0.0] Only inject metadata for outputs that cannot be reconstructed by skyf… (bazelbuild#16879) + 31e4bf4: Update java_tools v11.9 + cd40666: replace _get_canonical_form(label) with str(label) + e2bc237: Avoid exceptions from hermetic sandbox for unsupported artifact subclasses + b564d14: Remove warnings about ignored starlark options + 7ccc661: [6.0.0] Emit Tree objects in topological order (bazelbuild#16904) + 86dee6d: Correctly match regex with tree artifact + 14925b5: Always use target's attributes to set Python version (bazelbuild#16959) + a247502: Add 'toolchain' parameter to actions.{run,run_shell} + 497b7e4: Fix Bash `runfiles_current_repository` with RBE + 0a2c4ed: Fix corner cases in Bash runfiles library + 33b514b: Fix runfiles creation with MANIFEST when building without the bytes + 3a13af4: Remove LCOV merger dependency of `cc_test` without coverage (bazelbuild#17004) + 25ba76c: Include full tree artifact in inputs when prefetcher doesn't support partial tree artifacts. Incompatible changes: - this incompatible change breaks old instances of http_archive that specified netrc as an absolute path. It is unlikely there are many instances in the wild since the path would refer to a netrc file inside the external repository by absolute path. Migration should be straightforward. - genrule switched to use exec transition instead of host. This can break targets with hardcoded output paths. To avoid using hardcoded paths use make variables, see https://docs.bazel.build/versions/4.2.2/be/make-variables.html#pre defined_label_variables - this incompatible change breaks old instances of http_archive that specified netrc as an absolute path. It is unlikely there are many instances in the wild since... - Error Prone now checks for unused return values of additional methods on `java.lang.Object`, which can be disabled using `--javacopts=-Xep:ReturnValueIgnored:OFF` - Error Prone now checks for unused return values of additional methods on `java.lang.Object`, which can be disabled using `--javacopts=-Xep:ReturnValueIgnored:OFF` - The --incompatible_existing_rules_immutable_view flag has been flipped to true. See bazelbuild#13907 for migration notes. - Split up the C++ archive from the C++ link action and set `CppArchive` as mnemonic. - workspace(managed_directories=) is not available anymore. - --legacy_important_outputs now has a default of false. - --legacy_important_outputs default reverted to true. - objc_library now requires CcInfo in its deps. If this breaks you, add empty CcInfo() to your rule. - Flag --experimental_local_memory_estimate removed. - Added a new flag --incompatible_unambiguous_label_stringification, which causes labels in the main repo to stringify into unambiguous forms starting with an @. See bazelbuild#15916 for more information. - analysis_test moved into testing.analysis_test - Flip incompatible_enable_cc_toolchain_resolution (bazelbuild#7260) - (Rollback) Flip incompatible_enable_cc_toolchain_resolution (bazelbuild#7260) - name parameter is removed from rule call (bazelbuild#16301) - name parameter is removed from rule call (bazelbuild#16301) - name parameter is removed from rule call (bazelbuild#16301) - --incompatible_remote_downloader_send_all_headers is flipped to true. See bazelbuild#16356 for details. - GrpcRemoteDownloader only includes relevant headers instead of sending all credentials. - In package_group's `packages` attribute, the syntax "//..." now refers to all packages in the same repository as the package group, rather than all packages everywhere. The new item "public" can be used instead to obtain the old behavior. In `bazel query --output=proto` (and `--output=xml`), the `packages` attribute now serializes with the leading double slash included (for instance, `//foo/bar/...` instead of `foo/bar/...`). See also bazelbuild#16355, bazelbuild#16323, and bazelbuild#16391. - Bazel no longer increases the delay between progress updates when there is no cursor control. - `--incompatible_always_include_files_in_data` is flipped to true. See bazelbuild#16654 for details. - `cquery --output=files` also outputs source files. Closes bazelbuild#16602. - `--incompatible_strict_conflict_checks` is flipped to true. See bazelbuild#16729 for details. - This changes the behavior of Python version in exec/host configuration. Mitigation is to set Python version on the targets. New features: - Support local_repository in Bazel Registry's source.json file Important changes: - Deprecate --incompatible_applicable_licenses flag, in preparation for removal in Bazel 6.x. - Treat py_*.srcs_version="PY2" the same as "PY2ONLY". - The Build Event Protocol now contains file digests and sizes along with the file name and URI. - Refactor system suspend event handling. - alias() can now select() directly on constraint_value() - Allow \a \b \f \v escape sequences in Starlark. - Match remote and local xcode version by most granular version. - Adds `--experimental_worker_multiplex_sandboxing` flag that controls whether to sandbox multiplex workers that support it. - provider() has a new parameter: init, a callback for performing pre-processing and validation of field values. Iff this parameter is set, provider() returns a tuple of 2 elements: the usual provider symbol (which, when called, invokes init) and a raw constructor (which bypasses init). - Tests that fail to create or complete their `TestAttemptContinuation` by throwing an `ExecException` will report an `INCOMPLETE` status. Previously, Bazel would fail to report any status for the test attempt. - Fixed an issue where Bazel could erroneously report a test passes in coverage mode without actually running the test. - Include more information about configurations in cquery proto formatted output. This deprecates the configuration field of AnalysisProtosV2.ConfiguredTarget, and adds a new field, configuration_id, to be used instead. - experimental cc_library.implementation_deps inverted to interface_deps - In aquery and cquery proto output, indicate if a configuration is a tool or non-tool configuration. - Include complete configurations in cquery proto output. - experimental cc_library.implementation_deps inverted to interface_deps - Make protocOpts() publicly accessible. - Add some documentation about how configuration information is conveyed in cquery proto output. - Introduces experimental static library linking API under apple_common.link_multi_arch_static_library - Further deprecation and removal of pkg_tar. Stop supporting legacy use of 'files' attribute, where it could be a list of labels instead of a map of paths to labels. - Removed --incompatible_no_build_defs_pkg flag. It never fulfilled its purpose because --all_incompatible_changes would never set it. The last rule it gated (pkg_tar) is scheduled to be removed in Bazel 6.x. - Add coverage configuration fragment, used to expose output_generator label. - Bazel now no longer includes system headers on macOS in coverage reports (bazelbuild#14969). - android_sdk_repository read $ANDROID_SDK_ROOT in addition to $ANDROID_HOME. - The default dexer is now d8. dx can be optionally enabled using: --define=android_dexmerger_tool=dx_dexmerger \ --define=android_incremental_dexing_tool=dx_dexbuilder \ --define=android_standalone_dexing_tool=dx_compat_dx \ --use_workers_with_dexbuilder - Packaging support for deploy JAR embedded JDK files (hermetic Java). - Don't stamp cc_common.link actions for tool dependencies. - Starlark test rules can use the new inherited_environment parameter of testing.TestEnvironment to specify environment variables whose values should be inherited from the shell environment. - Enable merging permissions during Android manifest merging with the --merge_android_manifest_permissions flag. - Allow specialization to work with constraint_values. - Bazel uses the D8 jar from Maven instead of the SDK. - Make ijar / java_import preserve classes with `@kotlin.Metadata` annotations - Switch cc_test implementation to Starlark. Note: cc_test will now link statically when _targeting_ Windows regardless of host platform (rather than always linking statically when Windows is the _host_). - Switch cc_test implementation to Starlark. Note: cc_test will now link statically when _targeting_ Windows regardless of host platform (rather than always linking statically when Windows is the _host_). - Add devtools/build/lib/worker:work_request_handlers to the remote android tools release package. This will be transitively packaged into all_android_tools. - Bazel uses the D8 jar from Maven instead of the SDK. - android_sdk_repository read $ANDROID_SDK_ROOT in addition to $ANDROID_HOME. - Advance android_tools_pkg version to 0.24.0. - Switch cc_test implementation to Starlark. Note: cc_test will now link statically when _targeting_ Windows regardless of host platform (rather than always linking statically when Windows is the _host_). - Bazel uses the D8 jar from Maven instead of the SDK. - "blaze config" now only reports info from the last build. To compare configurations across multiple builds, redirect "blaze config" output to a file and run your favorite diff tool. - The --incompatible_override_toolchain_transition flag is now always set, and will be removed in the future. Thus, --noincompatible_override_toolchain_transition has no effect, and the value of the incompatible_use_toolchain_transition parameter in aspect() and rule() builtins is ignored. - Switch cc_test implementation to Starlark. Note: cc_test will now link statically when _targeting_ Windows regardless of host platform (rather than always linking statically when Windows is the _host_). - Toolchain types may now be optional, in addition to mandatory. See https://bazel.build/docs/toolchains#optional-toolchains for further details. - Add six to deps of has_services=1 py_proto_librarys. - pkg_tar(symlinks) has been removed. Users needing that feature should migrate to @rules_pkg. - Aspects can now define and use exec groups using the same API as rules. - Removed the obsolete --incompatible_applicable_licenses flag. The feature is permanently enabled. - embedded_tools packages R8 desugarer again - Bazel now selects sh path based on execution platform instead of host platform, making it possible to execute sh actions in multiplatform builds. --shell_executable now only applies to actions configured for host. - labels in genquery.scope are no longer configured. - When Bzlmod is enabled, all Bzlmod-generated repos will have an extra '@' prepended to their names. This effectively enables the canonical label literal syntax for Bzlmod-generated repos (`@@canonicalRepoName//pkg:target`; see https://docs.google.com/document/d/1N81qfCa8oskCk5LqTW-LNthy6EBrDo t7bdUsjz6JFC4/edit?usp=sharing). - Exposed `CcSharedLibraryInfo` to Starlark builtins. - Enable --use_top_level_targets_for_symlinks by default. - Singlejar accepts runtime Created-By field - --noincompatible_disable_managed_directories, and with that, workspace(managed_directories=) is not supported anymore. - Bazel supports D8 desugaring, albeit without persistent workers - Remove mtime options from pkg_tar. Users should migrate to @rules_pkg. - Test for experimental multiplexed persistent resource processor. - Added new register_{execution_platforms,toolchains} directives to the MODULE.bazel file, to replace the {execution_platforms,toolchains}_to_register attributes on the module() directive. - The legacy pkg_tar no longer supports the ability to untar and repackage an input tar file (`deps` attribute). Users needed that capability must switch to github.com/bazelbuild/rules_pkg. - `cquery`'s new output mode [`--output=files`](https://bazel.build/docs/cquery#files-output) lists the output files of the targets matching the query. It takes the current value of `--output_groups` into account. - Change singlejar metadata to report Created-By Bazel - Add support for fetching RPC credentials from credential helper. - Revert interface_deps back to implementation_deps after problem reported in. Use `buildozer 'rename deps implementation_deps' //...:%cc_library; buildozer 'rename interface_deps deps' //...:%cc_library` - Fix for desugaring failure on Bazel+Android+Windows build scenario. - D8 is the default desugarer - Migrate main_dex_list_creator to D8 (DX deprecation) - --experimental_enable_bzlmod has been renamed --enable_bzlmod, and still defaults to false. - selects() no longer produce irrelevant duplicate label checks - Adds a dexer output cache to CompatDexBuilder to improve build speed. - Improved error messages when analyzing inline bzl code - Improved error messages when analyzing inline bzl code - The `@bazel_tools//tools/cpp:compiler` flag now has the value `gcc` if the configured compiler is detected to be gcc rather than the generic value `compiler`. A branch for `gcc` may have to be added to `select` statements that do not have a default case that handles gcc appropriately. - The `get_child` method of `path` now accepts an arbitrary number of relative path strings as positional arguments. - SourceManifestAction supports `Action.content` - Add --incompatible_build_transitive_python_runfiles alias. See bazelbuild#16303 - The @bazel_tools//tools/cpp:compiler flag now has the value `clang` for the auto-configured Xcode toolchain rather than the generic value compiler. A branch for `clang` may have to be added to select statements that do not have a default case that handles this toolchain appropriately. - added additional debug message to warn of skipped toolchains during resolution - The deprecated --remote_allow_symlink_upload flag has been removed. Symlinks in local action outputs are always permitted, even with remote caching. Whether they're uploaded as symlinks or as the files/directories they point to is still determined by the --incompatible_remote_symlinks flag. - Added `struct`, `json`, `proto`, and `depset` to the starlark environment of Bazel's cquery (--output=starlark) command - Added three `package_group`-related flags: `--incompatible_package_group_includes_double_slash` (bazelbuild#16391), `--incompatible_package_group_has_public_syntax` (bazelbuild#16355), and `--incompatible_fix_package_group_reporoot_syntax` (bazelbuild#16323). With these flags, `package_group` can now easily specify "all packages", "no packages", and "all packages in the current repo". - Record hermetic packaged JDK modules file size in deploy JAR manifest 'JDK-Lib-Modules-Size' attribute. - .bzl files may now set a visibility to guard what other .bzl and BUILD files may load them. See [...] for more information. - Deletes the --extra_proguard_specs Blaze flag - 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 bazelbuild#16124 Fixes bazelbuild#10923 Closes bazelbuild#16428. - 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 This release contains contributions from many people at Google, as well as Adam Azarchs, Adam Singer, Adam Wolf, Albert Lloveras, Alessandro Patti, Alex Eagle, Alex Scott, Alex Torok, Andreas Fuchs, Andreas Herrmann, Andrew Katson, Andrew Klotz, Ara Nguyen, arunkumar9t2, arun.sampathkumar, Ast-x64, Benedek Thaler, Benjamin Lee, Benjamin Peterson, Ben Lee, Bohdan Vanieiev, Bo Zhang, Bo Zhang, Bradley Burns, Brandon Duffany, Brandon Jacklyn, Brentley Jones, Brentley Jones, Chad Miller, Charles-Francois Natali, Chris Clearwater, Chris Fredrickson, Christopher Peterson Sauer, Christopher Rydell, Christopher Sauer, ckiffel, Cristian Hancila, crydell-ericsson, Dan Fleming, Daniel Wagner-Hall, Danny Wolf, David Ostrovsky, David Sanderson, Denys Kurylenko, dhmemi, Dimi Shahbaz, divanorama, dmaclach, Ed Schouten, Emil Kattainen, Eric Song, Eric Wendelin, Fabian Brandstetter, Fabian Meumertzheim, floriographygoth, Fredrik Medley, George Prekas, gkgoat1, gkorlam, Greg Estren, Greg, Gregory Fong, Greg Roodt, Grzegorz Lukasik, Halil Sener, Hannes Kufler, homuler, hvadehra, hvd, Igor Nazarenko, James Broadhead, Jan, Jason Tan, Jay Bazuzi, Jeremy Volkman, jheaff1, Jiawen Chen, Joel Williamson, John Laxson, John Millikin, Jonathan Gerrish, Jon Shea, Jordan, juanchoviedo, Kaiqin Chen, Keith Smiley, Ken Micklas, Kevin Lin, Kirill Zabelin, Kiron, Krishna Ersson, Krzysztof Naglik, kshyanashree, lihu, Luc Bertrand, Luis Fernando Pino Duque, lunch-glide-pepper, Marek uppa, Matt Clarkson, Matt Mackay, Michael P. Nitowski, Mikhail Balabin, Mostyn Bramley-Moore, Nick Korostelev, Nitesh Anandan, Niyas Sait, Noa Resare, Olek Wojnar, Oscar Bonilla, Patrick Balestra, Paul Tarjan, Peter Mounce, Philipp Schrader, Pras Velagapudi, Rahul Butani, Rajeshwar Reddy T, Rifqi Mulya Fahmi, Roman Salvador, rustberry, Ryan Beasley, Ryan Schmidt, Sahin Yort, Saleem Abdulrasool, Sara Adams, Shuai Zhang, Simon Bjorklen, Son Luong Ngoc, Stephan Wolski, Steve Vermeulen, Stiopa Koltsov, Sven Tiffe, Takeo Sawada, Tao Wang, Ted Kaplan, Tetsuo Kiso, Thi Doan, Thomas Chen, ThomasCJY, Thomas, Thomas Zayouna, Timothe Peignier, Tomas Volf, Tom de Goede, UebelAndre, Ulf Adams, Ulrik Falklof, vardaro, Vasilios Pantazopoulos, Vladimir Tagakov, Waleed Khan, William Muir, Xavier Bonaventura, Xdng Yng, Xiangquan Xiao, Xùdōng Yáng, Yannic Bonenberger, Yannic Bonenberger, Yannic, Yannic, Yesudeep Mangalapilly, Yuval K, Zhongpeng Lin.

Baseline: d60ce2c Cherry picks: + 490f8ba: kshyanashree is the release manager of 6.0.0 + 4e66d93: Automated rollback of commit 2a28909. + 48a8d01: Allow C/C++ coverage collection for external targets + ec7be34: Temporarily set parent directory of the input to writable if it is not. + b098434: Infer CPUs for tvOS and watchOS when on Apple Silicon + 5cea7dd: Improve the documentation for ctx.actions.symlink. + a82d26f: Add quotes to "Tip" + 75b0f3a: Write a repo mapping manifest in the runfiles directory (#16555) + 07c5c1a: Ensure repository names don't start with `~` + 30f6c82: Escape tilde more gracefully + cf3f48c: Relax `Label` repo visibility validation + 4477823: Use "apparent name" instead of "local name" in Bzlmod docs + 55f4f48: Bazel DevSite: Add required css file. + a706994: Remove logic that increases delay between progress updates over time + 1d514ab: Remove references to io_bazel repository + b0357bd: Relnotes python script + 8f95651: Allow Java coverage collection for external targets + bddb191: Fix race condition in package-bazel.sh + a757852: Decanonicalize labels emitted by {a,c,}query if possible + 9d250ed: Add uniquify parameter to TemplateDict.add_joined + f02bcf8: Fix identical gcov json file name problem + a159330: Add `$(rlocationpath(s) ...)` expansion + 56f54da: Rollup of SBOM correctness fixes (#16655) + 72e6e94: [cc] Add cc toolchain to starlark cc_proto_library (#16661) + 8f28513: Make C++ runfiles library repo mapping aware + 95f9adc: Always collect FileProvider's filesToBuild as data runfiles + 4959d34: fix: export constraints.bzl file from @local_config_platform so it can be used in downstream bzl_library targets + 4919d4a: Add --host_per_file_copt (#16695) + 0a23d46: Moving some tests for `RemoteActionFileSystem` of BwoB to a base class. + 9296068: [remote/downloader] Don't include headers in `FetchBlobRequest` + 128d833: [remote] Respect whether the server supports action cache updates + 38c5019: [remote/downloader] Migrate `Downloader` to take `Credentials` (#16732) + 5929cb7: Stage repository mapping manifest as a root symlink (#16733) + 455454a: Expose current repository name to Java with @AutoBazelRepository + 97dea59: Implement getDirectoryEntries and readdir for RemoteActionFileSystem. + aa45f5f: Move integration tests for BwoB to a base class and add more tests there. + 1b073ac: Make Java runfiles library repo mapping aware + 148bbb1: Use `_repo_mapping` in C++ runfiles library (#16752) + 25558ad: Add --experimental_action_cache_store_output_metadata to the expansio… + 6e945e8: Treat `DEBUG` events as progress-like. + 1940c5d: redact 'token' strings from logging + 0b64525: Make Bash runfiles library repo mapping aware (#16753) + 4caae75: Automated rollback of commit 8f95651. + 13ff6d9: Fix Bash rlocation failure with stricter Bash options + bd88c7e: Make bazel Android remote deps compatible with bzlmod (#16772) + 6f6d4cc: Flip `--incompatible_always_include_files_in_data` + 94355b1: Add required `--add-opens` server JVM args also with non-embedded JDK + 8349c95: Also collect clang resource directory with `-no-canonical-prefixes` + dce6ed7: Make `bazel run` works with minimal mode + ca8674c: Include source files with `cquery --output=files` (#16826) + 9cb5e0a: Fsync before rename after copy in DiskCacheClient + 23ffce5: Update GetActionResult for disk cache to check referenced files when … + 0bc0ff5: Make Java runfiles library compilable with JDK 8 + fe16965: [6.0.0] Default --incompatible_strict_conflict_checks to true. (#16864) + 99ca86f: Revert "[6.0.0] Default --incompatible_strict_conflict_checks to true. (#16864)" (#16872) + 312238f: Make C++ runfiles library build with `-Werror=shadow` + 2baa5a4: Keep credentials cached across build commands. + 8818a57: [6.0.0] Only inject metadata for outputs that cannot be reconstructed by skyf… (#16879) + 31e4bf4: Update java_tools v11.9 + cd40666: replace _get_canonical_form(label) with str(label) + e2bc237: Avoid exceptions from hermetic sandbox for unsupported artifact subclasses + b564d14: Remove warnings about ignored starlark options + 7ccc661: [6.0.0] Emit Tree objects in topological order (#16904) + 86dee6d: Correctly match regex with tree artifact + 14925b5: Always use target's attributes to set Python version (#16959) + a247502: Add 'toolchain' parameter to actions.{run,run_shell} + 497b7e4: Fix Bash `runfiles_current_repository` with RBE + 0a2c4ed: Fix corner cases in Bash runfiles library + 33b514b: Fix runfiles creation with MANIFEST when building without the bytes + 3a13af4: Remove LCOV merger dependency of `cc_test` without coverage (#17004) + 25ba76c: Include full tree artifact in inputs when prefetcher doesn't support partial tree artifacts. Incompatible changes: - this incompatible change breaks old instances of http_archive that specified netrc as an absolute path. It is unlikely there are many instances in the wild since the path would refer to a netrc file inside the external repository by absolute path. Migration should be straightforward. - genrule switched to use exec transition instead of host. This can break targets with hardcoded output paths. To avoid using hardcoded paths use make variables, see https://docs.bazel.build/versions/4.2.2/be/make-variables.html#pre defined_label_variables - this incompatible change breaks old instances of http_archive that specified netrc as an absolute path. It is unlikely there are many instances in the wild since... - Error Prone now checks for unused return values of additional methods on `java.lang.Object`, which can be disabled using `--javacopts=-Xep:ReturnValueIgnored:OFF` - Error Prone now checks for unused return values of additional methods on `java.lang.Object`, which can be disabled using `--javacopts=-Xep:ReturnValueIgnored:OFF` - The --incompatible_existing_rules_immutable_view flag has been flipped to true. See #13907 for migration notes. - Split up the C++ archive from the C++ link action and set `CppArchive` as mnemonic. - workspace(managed_directories=) is not available anymore. - --legacy_important_outputs now has a default of false. - --legacy_important_outputs default reverted to true. - objc_library now requires CcInfo in its deps. If this breaks you, add empty CcInfo() to your rule. - Flag --experimental_local_memory_estimate removed. - Added a new flag --incompatible_unambiguous_label_stringification, which causes labels in the main repo to stringify into unambiguous forms starting with an @. See #15916 for more information. - analysis_test moved into testing.analysis_test - Flip incompatible_enable_cc_toolchain_resolution (#7260) - (Rollback) Flip incompatible_enable_cc_toolchain_resolution (#7260) - name parameter is removed from rule call (#16301) - name parameter is removed from rule call (#16301) - name parameter is removed from rule call (#16301) - --incompatible_remote_downloader_send_all_headers is flipped to true. See #16356 for details. - GrpcRemoteDownloader only includes relevant headers instead of sending all credentials. - In package_group's `packages` attribute, the syntax "//..." now refers to all packages in the same repository as the package group, rather than all packages everywhere. The new item "public" can be used instead to obtain the old behavior. In `bazel query --output=proto` (and `--output=xml`), the `packages` attribute now serializes with the leading double slash included (for instance, `//foo/bar/...` instead of `foo/bar/...`). See also #16355, #16323, and #16391. - Bazel no longer increases the delay between progress updates when there is no cursor control. - `--incompatible_always_include_files_in_data` is flipped to true. See #16654 for details. - `cquery --output=files` also outputs source files. Closes #16602. - `--incompatible_strict_conflict_checks` is flipped to true. See #16729 for details. - This changes the behavior of Python version in exec/host configuration. Mitigation is to set Python version on the targets. New features: - Support local_repository in Bazel Registry's source.json file Important changes: - Deprecate --incompatible_applicable_licenses flag, in preparation for removal in Bazel 6.x. - Treat py_*.srcs_version="PY2" the same as "PY2ONLY". - The Build Event Protocol now contains file digests and sizes along with the file name and URI. - Refactor system suspend event handling. - alias() can now select() directly on constraint_value() - Allow \a \b \f \v escape sequences in Starlark. - Match remote and local xcode version by most granular version. - Adds `--experimental_worker_multiplex_sandboxing` flag that controls whether to sandbox multiplex workers that support it. - provider() has a new parameter: init, a callback for performing pre-processing and validation of field values. Iff this parameter is set, provider() returns a tuple of 2 elements: the usual provider symbol (which, when called, invokes init) and a raw constructor (which bypasses init). - Tests that fail to create or complete their `TestAttemptContinuation` by throwing an `ExecException` will report an `INCOMPLETE` status. Previously, Bazel would fail to report any status for the test attempt. - Fixed an issue where Bazel could erroneously report a test passes in coverage mode without actually running the test. - Include more information about configurations in cquery proto formatted output. This deprecates the configuration field of AnalysisProtosV2.ConfiguredTarget, and adds a new field, configuration_id, to be used instead. - experimental cc_library.implementation_deps inverted to interface_deps - In aquery and cquery proto output, indicate if a configuration is a tool or non-tool configuration. - Include complete configurations in cquery proto output. - experimental cc_library.implementation_deps inverted to interface_deps - Make protocOpts() publicly accessible. - Add some documentation about how configuration information is conveyed in cquery proto output. - Introduces experimental static library linking API under apple_common.link_multi_arch_static_library - Further deprecation and removal of pkg_tar. Stop supporting legacy use of 'files' attribute, where it could be a list of labels instead of a map of paths to labels. - Removed --incompatible_no_build_defs_pkg flag. It never fulfilled its purpose because --all_incompatible_changes would never set it. The last rule it gated (pkg_tar) is scheduled to be removed in Bazel 6.x. - Add coverage configuration fragment, used to expose output_generator label. - Bazel now no longer includes system headers on macOS in coverage reports (#14969). - android_sdk_repository read $ANDROID_SDK_ROOT in addition to $ANDROID_HOME. - The default dexer is now d8. dx can be optionally enabled using: --define=android_dexmerger_tool=dx_dexmerger \ --define=android_incremental_dexing_tool=dx_dexbuilder \ --define=android_standalone_dexing_tool=dx_compat_dx \ --use_workers_with_dexbuilder - Packaging support for deploy JAR embedded JDK files (hermetic Java). - Don't stamp cc_common.link actions for tool dependencies. - Starlark test rules can use the new inherited_environment parameter of testing.TestEnvironment to specify environment variables whose values should be inherited from the shell environment. - Enable merging permissions during Android manifest merging with the --merge_android_manifest_permissions flag. - Allow specialization to work with constraint_values. - Bazel uses the D8 jar from Maven instead of the SDK. - Make ijar / java_import preserve classes with `@kotlin.Metadata` annotations - Switch cc_test implementation to Starlark. Note: cc_test will now link statically when _targeting_ Windows regardless of host platform (rather than always linking statically when Windows is the _host_). - Switch cc_test implementation to Starlark. Note: cc_test will now link statically when _targeting_ Windows regardless of host platform (rather than always linking statically when Windows is the _host_). - Add devtools/build/lib/worker:work_request_handlers to the remote android tools release package. This will be transitively packaged into all_android_tools. - Bazel uses the D8 jar from Maven instead of the SDK. - android_sdk_repository read $ANDROID_SDK_ROOT in addition to $ANDROID_HOME. - Advance android_tools_pkg version to 0.24.0. - Switch cc_test implementation to Starlark. Note: cc_test will now link statically when _targeting_ Windows regardless of host platform (rather than always linking statically when Windows is the _host_). - Bazel uses the D8 jar from Maven instead of the SDK. - "blaze config" now only reports info from the last build. To compare configurations across multiple builds, redirect "blaze config" output to a file and run your favorite diff tool. - The --incompatible_override_toolchain_transition flag is now always set, and will be removed in the future. Thus, --noincompatible_override_toolchain_transition has no effect, and the value of the incompatible_use_toolchain_transition parameter in aspect() and rule() builtins is ignored. - Switch cc_test implementation to Starlark. Note: cc_test will now link statically when _targeting_ Windows regardless of host platform (rather than always linking statically when Windows is the _host_). - Toolchain types may now be optional, in addition to mandatory. See https://bazel.build/docs/toolchains#optional-toolchains for further details. - Add six to deps of has_services=1 py_proto_librarys. - pkg_tar(symlinks) has been removed. Users needing that feature should migrate to @rules_pkg. - Aspects can now define and use exec groups using the same API as rules. - Removed the obsolete --incompatible_applicable_licenses flag. The feature is permanently enabled. - embedded_tools packages R8 desugarer again - Bazel now selects sh path based on execution platform instead of host platform, making it possible to execute sh actions in multiplatform builds. --shell_executable now only applies to actions configured for host. - labels in genquery.scope are no longer configured. - When Bzlmod is enabled, all Bzlmod-generated repos will have an extra '@' prepended to their names. This effectively enables the canonical label literal syntax for Bzlmod-generated repos (`@@canonicalRepoName//pkg:target`; see https://docs.google.com/document/d/1N81qfCa8oskCk5LqTW-LNthy6EBrDo t7bdUsjz6JFC4/edit?usp=sharing). - Exposed `CcSharedLibraryInfo` to Starlark builtins. - Enable --use_top_level_targets_for_symlinks by default. - Singlejar accepts runtime Created-By field - --noincompatible_disable_managed_directories, and with that, workspace(managed_directories=) is not supported anymore. - Bazel supports D8 desugaring, albeit without persistent workers - Remove mtime options from pkg_tar. Users should migrate to @rules_pkg. - Test for experimental multiplexed persistent resource processor. - Added new register_{execution_platforms,toolchains} directives to the MODULE.bazel file, to replace the {execution_platforms,toolchains}_to_register attributes on the module() directive. - The legacy pkg_tar no longer supports the ability to untar and repackage an input tar file (`deps` attribute). Users needed that capability must switch to github.com/bazelbuild/rules_pkg. - `cquery`'s new output mode [`--output=files`](https://bazel.build/docs/cquery#files-output) lists the output files of the targets matching the query. It takes the current value of `--output_groups` into account. - Change singlejar metadata to report Created-By Bazel - Add support for fetching RPC credentials from credential helper. - Revert interface_deps back to implementation_deps after problem reported in. Use `buildozer 'rename deps implementation_deps' //...:%cc_library; buildozer 'rename interface_deps deps' //...:%cc_library` - Fix for desugaring failure on Bazel+Android+Windows build scenario. - D8 is the default desugarer - Migrate main_dex_list_creator to D8 (DX deprecation) - --experimental_enable_bzlmod has been renamed --enable_bzlmod, and still defaults to false. - selects() no longer produce irrelevant duplicate label checks - Adds a dexer output cache to CompatDexBuilder to improve build speed. - Improved error messages when analyzing inline bzl code - Improved error messages when analyzing inline bzl code - The `@bazel_tools//tools/cpp:compiler` flag now has the value `gcc` if the configured compiler is detected to be gcc rather than the generic value `compiler`. A branch for `gcc` may have to be added to `select` statements that do not have a default case that handles gcc appropriately. - The `get_child` method of `path` now accepts an arbitrary number of relative path strings as positional arguments. - SourceManifestAction supports `Action.content` - Add --incompatible_build_transitive_python_runfiles alias. See #16303 - The @bazel_tools//tools/cpp:compiler flag now has the value `clang` for the auto-configured Xcode toolchain rather than the generic value compiler. A branch for `clang` may have to be added to select statements that do not have a default case that handles this toolchain appropriately. - added additional debug message to warn of skipped toolchains during resolution - The deprecated --remote_allow_symlink_upload flag has been removed. Symlinks in local action outputs are always permitted, even with remote caching. Whether they're uploaded as symlinks or as the files/directories they point to is still determined by the --incompatible_remote_symlinks flag. - Added `struct`, `json`, `proto`, and `depset` to the starlark environment of Bazel's cquery (--output=starlark) command - Added three `package_group`-related flags: `--incompatible_package_group_includes_double_slash` (#16391), `--incompatible_package_group_has_public_syntax` (#16355), and `--incompatible_fix_package_group_reporoot_syntax` (#16323). With these flags, `package_group` can now easily specify "all packages", "no packages", and "all packages in the current repo". - Record hermetic packaged JDK modules file size in deploy JAR manifest 'JDK-Lib-Modules-Size' attribute. - .bzl files may now set a visibility to guard what other .bzl and BUILD files may load them. See [...] for more information. - Deletes the --extra_proguard_specs Blaze flag - 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 Fixes #10923 Closes #16428. - 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 This release contains contributions from many people at Google, as well as Adam Azarchs, Adam Singer, Adam Wolf, Albert Lloveras, Alessandro Patti, Alex Eagle, Alex Scott, Alex Torok, Andreas Fuchs, Andreas Herrmann, Andrew Katson, Andrew Klotz, Ara Nguyen, arunkumar9t2, arun.sampathkumar, Ast-x64, Benedek Thaler, Benjamin Lee, Benjamin Peterson, Ben Lee, Bohdan Vanieiev, Bo Zhang, Bo Zhang, Bradley Burns, Brandon Duffany, Brandon Jacklyn, Brentley Jones, Brentley Jones, Chad Miller, Charles-Francois Natali, Chris Clearwater, Chris Fredrickson, Christopher Peterson Sauer, Christopher Rydell, Christopher Sauer, ckiffel, Cristian Hancila, crydell-ericsson, Dan Fleming, Daniel Wagner-Hall, Danny Wolf, David Ostrovsky, David Sanderson, Denys Kurylenko, dhmemi, Dimi Shahbaz, divanorama, dmaclach, Ed Schouten, Emil Kattainen, Eric Song, Eric Wendelin, Fabian Brandstetter, Fabian Meumertzheim, floriographygoth, Fredrik Medley, George Prekas, gkgoat1, gkorlam, Greg Estren, Greg, Gregory Fong, Greg Roodt, Grzegorz Lukasik, Halil Sener, Hannes Kufler, homuler, hvadehra, hvd, Igor Nazarenko, James Broadhead, Jan, Jason Tan, Jay Bazuzi, Jeremy Volkman, jheaff1, Jiawen Chen, Joel Williamson, John Laxson, John Millikin, Jonathan Gerrish, Jon Shea, Jordan, juanchoviedo, Kaiqin Chen, Keith Smiley, Ken Micklas, Kevin Lin, Kirill Zabelin, Kiron, Krishna Ersson, Krzysztof Naglik, kshyanashree, lihu, Luc Bertrand, Luis Fernando Pino Duque, lunch-glide-pepper, Marek uppa, Matt Clarkson, Matt Mackay, Michael P. Nitowski, Mikhail Balabin, Mostyn Bramley-Moore, Nick Korostelev, Nitesh Anandan, Niyas Sait, Noa Resare, Olek Wojnar, Oscar Bonilla, Patrick Balestra, Paul Tarjan, Peter Mounce, Philipp Schrader, Pras Velagapudi, Rahul Butani, Rajeshwar Reddy T, Rifqi Mulya Fahmi, Roman Salvador, rustberry, Ryan Beasley, Ryan Schmidt, Sahin Yort, Saleem Abdulrasool, Sara Adams, Shuai Zhang, Simon Bjorklen, Son Luong Ngoc, Stephan Wolski, Steve Vermeulen, Stiopa Koltsov, Sven Tiffe, Takeo Sawada, Tao Wang, Ted Kaplan, Tetsuo Kiso, Thi Doan, Thomas Chen, ThomasCJY, Thomas, Thomas Zayouna, Timothe Peignier, Tomas Volf, Tom de Goede, UebelAndre, Ulf Adams, Ulrik Falklof, vardaro, Vasilios Pantazopoulos, Vladimir Tagakov, Waleed Khan, William Muir, Xavier Bonaventura, Xdng Yng, Xiangquan Xiao, Xùdōng Yáng, Yannic Bonenberger, Yannic Bonenberger, Yannic, Yannic, Yesudeep Mangalapilly, Yuval K, Zhongpeng Lin.

Baseline: 0a47a1f Incompatible changes: - Removing java_common.javac_jar Starlark call. - native.existing_rule now returns select values in a form that is accepted by rule instantiation. This is a breaking API change because there is some code that relies on the precise type returned, including brittle workarounds for this bug specifically and insufficiently flexible workarounds for other issues with the intersection of select and native.existing_rule. - flipped incompatible_use_toolchain_resolution_for_java_rules, see #7849 - Query output=xml/proto/location for source files will now show the location of line 1 of the source file (as the new default) instead of its location in the BUILD file. - Specifying a target pattern underneath a directory specified by .bazelignore will now emit a warning, not an error. - Query `--order_output=auto` will now sort lexicographically. However, when `somepath` is used as a top level function (e.g. `query 'somepath(a, b)'`), it will continue to output in dependency order. If you do not want the lexicographical output ordering, specify another `--order_output` value (`no`, `deps` or `full`) based on what ordering you require. - In the build event stream, BuildMetrics.TargetMetrics.targets_loaded is no longer populated. Its value was always mostly meaningless. BuildMetrics.TargetMetrics.targets_configured and BuildMetrics.ActionSummary.actions_created now include configured aspect data. - //visibility:legacy_public has been removed. - Flip and remove incompatible_dont_collect_so_artifacts (#13043). - Remove flag --experimental_no_product_name_out_symlink: it is always true. - The Starlark method generate_dsym in objc fragment has been deleted. Please use the equivalent apple_generate_dsym in cpp fragment instead. - Native libraries in data attribute are not collected. See #13550 for details - Enforce the `--profile` path to be absolute. - Enforce the --memory_profile path to be absolute. - JavaToolchainInfo.jvm_opt returns Depset instead of a list. - --apple_sdk has been deleted. It is a no-op. - --bep_publish_used_heap_size_post_build is now a no-op and will be deleted in a future release. Use --memory_profile=/dev/null instead. - Flipped --incompatible_disallow_resource_jars (see #13221). - Remove --bep_publish_used_heap_size_post_build - JSON trace profile: rename counter names. - Removed --action_graph from the dump command. - Remove `--{experimental_,}json_trace_compression` option. - Remove `--experimental_profile_cpu_usage`. - flipped --incompatible_java_common_parameters (see #12373) - this incompatible change breaks old instances of http_archive that specified netrc as an absolute path. It is unlikely there are many instances in the wild since the path would refer to a netrc file inside the external repository by absolute path. Migration should be straightforward. - genrule switched to use exec transition instead of host. This can break targets with hardcoded output paths. To avoid using hardcoded paths use make variables, see https://docs.bazel.build/versions/4.2.2/be/make-variables.html#pre defined_label_variables - this incompatible change breaks old instances of http_archive that specified netrc as an absolute path. It is unlikely there are many instances in the wild since... - Error Prone now checks for unused return values of additional methods on `java.lang.Object`, which can be disabled using `--javacopts=-Xep:ReturnValueIgnored:OFF` - Error Prone now checks for unused return values of additional methods on `java.lang.Object`, which can be disabled using `--javacopts=-Xep:ReturnValueIgnored:OFF` - The --incompatible_existing_rules_immutable_view flag has been flipped to true. See #13907 for migration notes. - Split up the C++ archive from the C++ link action and set `CppArchive` as mnemonic. - workspace(managed_directories=) is not available anymore. - --legacy_important_outputs now has a default of false. - --legacy_important_outputs default reverted to true. - objc_library now requires CcInfo in its deps. If this breaks you, add empty CcInfo() to your rule. - Flag --experimental_local_memory_estimate removed. - Added a new flag --incompatible_unambiguous_label_stringification, which causes labels in the main repo to stringify into unambiguous forms starting with an @. See #15916 for more information. - analysis_test moved into testing.analysis_test - Flip incompatible_enable_cc_toolchain_resolution (#7260) - (Rollback) Flip incompatible_enable_cc_toolchain_resolution (#7260) - name parameter is removed from rule call (#16301) - name parameter is removed from rule call (#16301) - name parameter is removed from rule call (#16301) - --incompatible_remote_downloader_send_all_headers is flipped to true. See #16356 for details. - GrpcRemoteDownloader only includes relevant headers instead of sending all credentials. - In package_group's `packages` attribute, the syntax "//..." now refers to all packages in the same repository as the package group, rather than all packages everywhere. The new item "public" can be used instead to obtain the old behavior. In `bazel query --output=proto` (and `--output=xml`), the `packages` attribute now serializes with the leading double slash included (for instance, `//foo/bar/...` instead of `foo/bar/...`). See also #16355, #16323, and #16391. - 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 #16729 for details. - `--incompatible_strict_conflict_checks` is flipped to true. See #16729 for details. - `--incompatible_always_include_files_in_data` is flipped to true. See #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 #16303 for details - --incompatible_python_disable_py2 is flipped to true. See #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 #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 (#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: - Args.add_all and Args.add_joined can now accept closures in map_each if explicitly enabled via allow_closure. - Add `--bes_header` flag to pass extra headers to the BES server. - Support local_repository in Bazel Registry's source.json file - The `aquery` and `cquery` commands now respect the `--query_file` flag just like the `query` command. Important changes: - Flag --incompatible_objc_compile_info_migration is removed. See #10854. - Flag --incompatible_objc_compile_info_migration is removed. See #10854. - Flag --incompatible_objc_compile_info_migration is removed. See #10854. - none PAIR=cmita - The --incompatible_load_python_rules_from_bzl flag is now a no-op. - Filter all (instead of just C++) source files for coverage output according to --instrumentation_filter and --instrument_test_targets. - The `--incompatible_disable_native_apple_binary_rule` flag has been added which disables the native `apple_binary` rule. Users who need to use `apple_binary` directly (if they cannot use one of the more specific Apple rules) should load it from https://github.com/bazelbuild/rules_apple. - The Android rules' --use_singlejar_apkbuilder is now a no-op. SingleJar will always be used to build APKs. - dict.setdefault(key, ...) now fails if dict is frozen, even if it already contains key. This is an incompatible API change. - Flag --incompatible_objc_provider_remove_compile_info is removed. See #11359. - Starlark now permits def statements to be nested (closures). - native.existing_rule now returns select values in a form that is accepted by rule instantiation. This is a breaking API change, though the fallout is expected to be small. - Starlark now supports lambda (anonymous function) expressions. - The "test" and "coverage" commands no longer return 3 when a test action fails because of a system error. Instead, the exit code reflects the type of system error. - The undocumented ctx.expand feature no longer exists. - Make --legacy_dynamic_scheduler a no-op flag. - Multiplex persistent workers can now use the JSON protocol. - native.existing_rule now returns a mutable list, not a tuple, for a list-valued attributes. This is an incompatible API change. - Roll back change to have native.existing_rules use list instead of tuple. - BEP includes test suite expansions. - config_setting now honors `visibility` attribute (and defaults to `//visibility:public`) - Change the MultiArchSplitTransitionProvider to be based on platform type + CPU instead of fixed "ios_" + cpu. - enforce config_setting visibility. See #12932 for details. - add a flag to build v4 signature file - Added _direct_source_jars output group to Java related targets. END_PUBLIC - pkg_deb is no longer part of @bazel_tools//build_defs/pkg:pkg.bzl. Use https://github.com/bazelbuild/rules_pkg/tree/main/pkg instead - Allowing the lipo operations to be conditional in the linkMultiArchBinary API for Apple binaries. Single architecture slices are now returned through AppleBinaryOutput and the Starlark API. - Release restriction for "-" in the package name for Python sources. Now `py_binary` and `py_test` targets can have main source file with "-" in the path. - Users consuming BEP may assume that a `named_set_of_files` event will appear before any event referencing that `named_set` by ID. This allows consumers to process the files for such events (eg. `TargetCompleted`) immediately. - BEP includes all files from successful actions in requested output groups. Previously, an output group's files were excluded if any file in the output group was not produced due to a failing action. Users can expect BEP output to be larger for failed builds. - In BEP, TargetComplete.output_group has a new field `incomplete` indicating that the file_sets field is missing one or more declared artifacts whose generating actions failed. - The flag `--toolchain_resolution_debug` now takes a regex argument, which is used to check which toolchain types should have debug info printed. You may use `.*` as an argument to keep the current behavior of debugging every toolchain type. - Add runfiles.merge_all() for merging a sequence of runfiles objects. - runfiles.merge() and merge_all() now respect --nested_set_depth_limit. If you hit the depth limit because you were calling merge() in a loop, use merge_all() on a sequence of runfiles objects instead. - Bazel will no longer create a bazel-out symlink if --symlink_prefix is specified: the directory pointed to via the bazel-out symlink is accessible via ${symlink_prefix}-out. If this causes problems for you, set --experimental_no_product_name_out_symlink=false in your builds and file an issue. - Updates worker protocol with cancellation fields, and adds experimental_worker_cancellation flag to control cancellation. - Simplify build failure output by always using `NNN arguments`. - trim_test_configuration now defaults to on - Mark genrule.srcs as a source attribute for coverage. - When using --allow_analysis_failures (for example, via bazel-skylib's analysistest with `expect_failure = True`), analysis-time failures in aspect implementation functions will now be propagated and saved in AnalysisFailureInfo, just like analysis-time failures in rules. - cquery --noimplicit_deps now correctly filters out resolved cc_toolchains - Sign apks deterministically. - Make gcov optional in cc_toolchain tools. - If --experimental_prefer_mutual_xcode is passed, Bazel will choose the local default (instead of the newest mutually available version) if it's available both locally and remotely. - Remove java_lite_proto_library.strict_deps attribute. - Generate proguard configurations deterministically. - Adds a new flag, `--incompatible_enable_cc_test_feature` which switches from the use of build variables to the feature of the same name. - Dropped fragile xz support from built in pkg_tar. Users requiring xz compression should switch to bazlebuild/rules_pkg. - If all strategies of one branch (the local or remote execution branch) of the `dynamic` strategy fail to even accept (via the response they give from `canExec`) the action, `dynamic` will now try to see if the other branch can accept it. (Trying to run it and it failing will still cause a failure if it was the first result, this is about strategies claiming they can't even try the action) - Add `disable_annotation_processing` option to `java_common.compile`, which disables any annotation processors passed to `plugins` or in `exported_plugins` of `deps` - Remove obsolete --incompatible_prohibit_aapt1 - The minimum Android build tools version for the Android rules is now 30.0.0 - Adds --experimental_reuse_sandbox_directories flag to reuse already-created non-worker sandboxes with cleanup. - --experimental_force_gc_after_build is deprecated and will be removed soon. Use --bep_publish_used_heap_size_post_build instead - Forward coverage-instrumented files from non-tool dependencies by default. - The used_heap_size_post_build field in BEP is populated when the --memory_profile flag is set - --run_validations defaults to true. - Consider label_keyed_string_dict attributes when gathering instrumented files for coverage. - Remove flag --experimental_forward_instrumented_files_info_by_default, now that this behavior is the default. - When using MemoryProfiler with multiple GCs via the --memory_profile_stable_heap_parameters flag, we do a more precise calculation of heap used at the end of the build. This will generally result in lower values. - --bep_publish_used_heap_size_post_build is deprecated. Use --memory_profile=/dev/null instead. - Disable --all_incompatible_changes flag. - The --all_incompatible_changes flag is now a no-op - The `--toolchain_resolution_debug` flag now accepts regexes matching targets, as well as toolchain types, when choosing what debug messages to print. - Adds --experimental_existing_rules_immutable_view flag to make the native.existing_rule and native.existing_rules functions more efficient by returning immutable, lightweight dict-like view objects instead of mutable dicts. - Add support to length-delimited protos as undeclared output annotations [] - The deprecated "relative_to_caller_repository" parameter has been removed from the Label constructor. - The toolchain transition is now enabled for all toolchains. - incompatible_disable_depset_items is flipped - The --experimental_existing_rules_immutable_view flag has been renamed to --incompatible_existing_rules_immutable_view - Bazel no longer supports Java 8. From this version on, the minimum required JDK is OpenJDK 11. - Deprecate --incompatible_applicable_licenses flag, in preparation for removal in Bazel 6.x. - Treat py_*.srcs_version="PY2" the same as "PY2ONLY". - The Build Event Protocol now contains file digests and sizes along with the file name and URI. - Refactor system suspend event handling. - alias() can now select() directly on constraint_value() - Allow \a \b \f \v escape sequences in Starlark. - Match remote and local xcode version by most granular version. - Adds `--experimental_worker_multiplex_sandboxing` flag that controls whether to sandbox multiplex workers that support it. - provider() has a new parameter: init, a callback for performing pre-processing and validation of field values. Iff this parameter is set, provider() returns a tuple of 2 elements: the usual provider symbol (which, when called, invokes init) and a raw constructor (which bypasses init). - Tests that fail to create or complete their `TestAttemptContinuation` by throwing an `ExecException` will report an `INCOMPLETE` status. Previously, Bazel would fail to report any status for the test attempt. - Fixed an issue where Bazel could erroneously report a test passes in coverage mode without actually running the test. - Include more information about configurations in cquery proto formatted output. This deprecates the configuration field of AnalysisProtosV2.ConfiguredTarget, and adds a new field, configuration_id, to be used instead. - experimental cc_library.implementation_deps inverted to interface_deps - In aquery and cquery proto output, indicate if a configuration is a tool or non-tool configuration. - Include complete configurations in cquery proto output. - experimental cc_library.implementation_deps inverted to interface_deps - Make protocOpts() publicly accessible. - Add some documentation about how configuration information is conveyed in cquery proto output. - Introduces experimental static library linking API under apple_common.link_multi_arch_static_library - Further deprecation and removal of pkg_tar. Stop supporting legacy use of 'files' attribute, where it could be a list of labels instead of a map of paths to labels. - Removed --incompatible_no_build_defs_pkg flag. It never fulfilled its purpose because --all_incompatible_changes would never set it. The last rule it gated (pkg_tar) is scheduled to be removed in Bazel 6.x. - Add coverage configuration fragment, used to expose output_generator label. - Bazel now no longer includes system headers on macOS in coverage reports (#14969). - android_sdk_repository read $ANDROID_SDK_ROOT in addition to $ANDROID_HOME. - The default dexer is now d8. dx can be optionally enabled using: --define=android_dexmerger_tool=dx_dexmerger \ --define=android_incremental_dexing_tool=dx_dexbuilder \ --define=android_standalone_dexing_tool=dx_compat_dx \ --use_workers_with_dexbuilder - Packaging support for deploy JAR embedded JDK files (hermetic Java). - Don't stamp cc_common.link actions for tool dependencies. - Starlark test rules can use the new inherited_environment parameter of testing.TestEnvironment to specify environment variables whose values should be inherited from the shell environment. - Enable merging permissions during Android manifest merging with the --merge_android_manifest_permissions flag. - Allow specialization to work with constraint_values. - Bazel uses the D8 jar from Maven instead of the SDK. - Make ijar / java_import preserve classes with `@kotlin.Metadata` annotations - Switch cc_test implementation to Starlark. Note: cc_test will now link statically when _targeting_ Windows regardless of host platform (rather than always linking statically when Windows is the _host_). - Switch cc_test implementation to Starlark. Note: cc_test will now link statically when _targeting_ Windows regardless of host platform (rather than always linking statically when Windows is the _host_). - Add devtools/build/lib/worker:work_request_handlers to the remote android tools release package. This will be transitively packaged into all_android_tools. - Bazel uses the D8 jar from Maven instead of the SDK. - android_sdk_repository read $ANDROID_SDK_ROOT in addition to $ANDROID_HOME. - Advance android_tools_pkg version to 0.24.0. - Switch cc_test implementation to Starlark. Note: cc_test will now link statically when _targeting_ Windows regardless of host platform (rather than always linking statically when Windows is the _host_). - Bazel uses the D8 jar from Maven instead of the SDK. - "blaze config" now only reports info from the last build. To compare configurations across multiple builds, redirect "blaze config" output to a file and run your favorite diff tool. - The --incompatible_override_toolchain_transition flag is now always set, and will be removed in the future. Thus, --noincompatible_override_toolchain_transition has no effect, and the value of the incompatible_use_toolchain_transition parameter in aspect() and rule() builtins is ignored. - Switch cc_test implementation to Starlark. Note: cc_test will now link statically when _targeting_ Windows regardless of host platform (rather than always linking statically when Windows is the _host_). - Toolchain types may now be optional, in addition to mandatory. See https://bazel.build/docs/toolchains#optional-toolchains for further details. - Add six to deps of has_services=1 py_proto_librarys. - pkg_tar(symlinks) has been removed. Users needing that feature should migrate to @rules_pkg. - Aspects can now define and use exec groups using the same API as rules. - Removed the obsolete --incompatible_applicable_licenses flag. The feature is permanently enabled. - embedded_tools packages R8 desugarer again - Bazel now selects sh path based on execution platform instead of host platform, making it possible to execute sh actions in multiplatform builds. --shell_executable now only applies to actions configured for host. - labels in genquery.scope are no longer configured. - When Bzlmod is enabled, all Bzlmod-generated repos will have an extra '@' prepended to their names. This effectively enables the canonical label literal syntax for Bzlmod-generated repos (`@@canonicalRepoName//pkg:target`; see https://docs.google.com/document/d/1N81qfCa8oskCk5LqTW-LNthy6EBrDo t7bdUsjz6JFC4/edit?usp=sharing). - Exposed `CcSharedLibraryInfo` to Starlark builtins. - Enable --use_top_level_targets_for_symlinks by default. - Singlejar accepts runtime Created-By field - --noincompatible_disable_managed_directories, and with that, workspace(managed_directories=) is not supported anymore. - Bazel supports D8 desugaring, albeit without persistent workers - Remove mtime options from pkg_tar. Users should migrate to @rules_pkg. - Test for experimental multiplexed persistent resource processor. - Added new register_{execution_platforms,toolchains} directives to the MODULE.bazel file, to replace the {execution_platforms,toolchains}_to_register attributes on the module() directive. - The legacy pkg_tar no longer supports the ability to untar and repackage an input tar file (`deps` attribute). Users needed that capability must switch to github.com/bazelbuild/rules_pkg. - `cquery`'s new output mode [`--output=files`](https://bazel.build/docs/cquery#files-output) lists the output files of the targets matching the query. It takes the current value of `--output_groups` into account. - Change singlejar metadata to report Created-By Bazel - Add support for fetching RPC credentials from credential helper. - Revert interface_deps back to implementation_deps after problem reported in. Use `buildozer 'rename deps implementation_deps' //...:%cc_library; buildozer 'rename interface_deps deps' //...:%cc_library` - Fix for desugaring failure on Bazel+Android+Windows build scenario. - D8 is the default desugarer - Migrate main_dex_list_creator to D8 (DX deprecation) - --experimental_enable_bzlmod has been renamed --enable_bzlmod, and still defaults to false. - selects() no longer produce irrelevant duplicate label checks - Adds a dexer output cache to CompatDexBuilder to improve build speed. - Improved error messages when analyzing inline bzl code - Improved error messages when analyzing inline bzl code - The `@bazel_tools//tools/cpp:compiler` flag now has the value `gcc` if the configured compiler is detected to be gcc rather than the generic value `compiler`. A branch for `gcc` may have to be added to `select` statements that do not have a default case that handles gcc appropriately. - The `get_child` method of `path` now accepts an arbitrary number of relative path strings as positional arguments. - SourceManifestAction supports `Action.content` - Add --incompatible_build_transitive_python_runfiles alias. See #16303 - The @bazel_tools//tools/cpp:compiler flag now has the value `clang` for the auto-configured Xcode toolchain rather than the generic value compiler. A branch for `clang` may have to be added to select statements that do not have a default case that handles this toolchain appropriately. - added additional debug message to warn of skipped toolchains during resolution - The deprecated --remote_allow_symlink_upload flag has been removed. Symlinks in local action outputs are always permitted, even with remote caching. Whether they're uploaded as symlinks or as the files/directories they point to is still determined by the --incompatible_remote_symlinks flag. - Added `struct`, `json`, `proto`, and `depset` to the starlark environment of Bazel's cquery (--output=starlark) command - Added three `package_group`-related flags: `--incompatible_package_group_includes_double_slash` (#16391), `--incompatible_package_group_has_public_syntax` (#16355), and `--incompatible_fix_package_group_reporoot_syntax` (#16323). With these flags, `package_group` can now easily specify "all packages", "no packages", and "all packages in the current repo". - Record hermetic packaged JDK modules file size in deploy JAR manifest 'JDK-Lib-Modules-Size' attribute. - .bzl files may now set a visibility to guard what other .bzl and BUILD files may load them. See [...] for more information. - Deletes the --extra_proguard_specs Blaze flag - 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 #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`. - `--experimental_remote_cache_compression` has been renamed to `--remote_cache_compression` - The REPO.bazel and MODULE.bazel files are now also considered workspace boundary markers. This release contains contributions from many people at Google, as well as Adam Azarchs, Adam Lavin, Adam Liddell, Adam Singer, Adam Wolf, Albert Lloveras, Alessandro Patti, Alex Eagle, Alex Eagle, Alex Eagle, Alex Scott, AlexTereshenkov, Alex Torok, Amanda L Martin, Andreas Fuchs, Andreas Herrmann, Andreas Herrmann, Andrew Katson, Andrew Klotz, Andy Hamon, Ankush Goyal, Anthony Pratti, Anthony Ter-Saakov, Ara Nguyen, Artem V. Navrotskiy, Artem Zinnatullin, arunkumar9t2, arun.sampathkumar, aryeh, Ast-x64, Austin Schuh, Benedek Thaler, Benjamin Lee, Benjamin Peterson, Benjamin Peterson, Benjamin Sigonneau, Ben Lee, Bohdan Vanieiev, Bo Zhang, Bo Zhang, Bradley Burns, Brandon Duffany, Brandon Jacklyn, Brentley Jones, Brentley Jones, bromano, Cameron Mulhern, Chad Miller, Charles-Francois Natali, Chirag Ramani, Chris Clearwater, Chris Fredrickson, Christopher Peterson Sauer, Christopher Rydell, Christopher Sauer, ckiffel, Cristian Hancila, crydell-ericsson, Dan Bamikiya, Dan Fleming, Daniel Grunwald, Daniel KT, Daniel McCarney, Daniel Wagner-Hall, Danny Wolf, Dave MacLachlan, Dave Nicponski, David Cummings, David, David Ostrovsky, David Sanderson, Delwin9999, Denys Kurylenko, dhmemi, Dimi Shahbaz, divanorama, dmaclach, Dmitry Ivankov, dorranh, ecngtng, Ed Schouten, Eitan Adler, Elliotte Rusty Harold, Emil Kattainen, erenon, Eric Cousineau, Eric Song, Eric Wendelin, Ethan Steinberg, Ezekiel Warren, Fabian Brandstetter, Fabian Meumertzheim, Fabian Meumertzheim, FaBrand, Fahrzin Hemmati, Fahrzin Hemmati, Felix Ehrenpfort, Finn Ball, floriographygoth, frazze-jobb, Fredrik Medley, Garrett Holmstrom, Gaspare Vitta, Gautam Korlam, George Gensure, George Prekas, gkgoat1, gkorlam, goodspark, Greg Estren, Greg, Greg Magolan, Gregory Fong, Greg Roodt, Grzegorz Lukasik, Grzegorz Lukasik, Halil Sener, Halil Sener, Hannes Kufler, Hao Yuan, homuler, hvadehra, hvd, Igor Nazarenko, Ikko Ashimine, Jack Dai, James Broadhead, James Ma, Jan, Jason Tan, Jay Bazuzi, Jeremy Volkman, Jesse Chan, jheaff1, Jiawen Chen, Joe Lencioni, Joel Jeske, Joel Williamson, Johannes Abt, John Hinnegan, John Laxson, John Laxson, John Millikin, Jonathan Gerrish, Jonathan Schear, Jon Landis, Jon Parise, jonrose-dev, Jon Shea, Jordan, juanchoviedo, Julio Merino, Justus Tumacder, Kaiqin Chen, keertk, Keith Smiley, kekxv, Ken Micklas, Kevin Hogeland, Kevin Lin, Kirill Zabelin, Kiron, Konstantin Erman, Krishna Ersson, Krzysztof Naglik, kshyanashree, Kun-Lu, Lauri Peltonen, Lee Mracek, lihu, Liu Liu, lripoche, Lszl Csomor, Luc Bertrand, Luis Fernando Pino Duque, m, Malte Poll, Marc Zych, Marc Zych, Marek uppa, Mark Karpov, Masoud Koleini, Mathieu Olivari, Matt Clarkson, Matt Mackay, Mauricio Galindo, Max Liu, Maxwell Elliott, Menny Even Danan, menny, Michael Chinen, Michael P. Nitowski, Mikhail Balabin, mohamadk, Mostyn Bramley-Moore, Nathaniel Brough, nathyong, Nick Korostelev, Niek Peeters, Nikolay Shelukhin, Nitesh Anandan, Niyas Sait, Noa Resare, odisseus, Oleh Stolyar, Olek Wojnar, Oliver Lee, Olle Lundberg, Omar Zuniga, Oscar Bonilla, Patrick Balestra, Patrick Balestra, Paul Gschwendtner, Paul Tarjan, Peter Kasting, Peter Mounce, Philipp Schrader, Pras Velagapudi, Qais Patankar, Rabi Shanker Guha, Rahul Butani, Rai, Rajeshwar Reddy T, Red Daly, redwrasse, Rifqi Mulya Fahmi, robincaloudis, Robin Tweedie, Roger Hu, Roman Salvador, ron-stripe, rustberry, Ryan Beasley, Ryan Schmidt, Sagar Pathare, Sahin Yort, Saleem Abdulrasool, samhowes, Samuel Giddins, Sara Adams, Sascha Moecker, Sebastian Olsson, Sergey Tyurin, Severin Strobl, Shuai Zhang, Siddhesh Bhupendra Kuakde, Simon Bjorklen, Simon Mavi Stewart, something_vague, Son Luong Ngoc, Stephan Wolski, Steve Siano, steve-the-bayesian, Steve Vermeulen, Stiopa Koltsov, susinmotion, Sven Tiffe, Takeo Sawada, Tao Wang, tatiana, tbaing, Ted Kaplan, Ted Kaplan, Tetsuo Kiso, Thaler Benedek, Thi Doan, Thi Doan, Thi Don, Thomas Carmet, Thomas Chen, ThomasCJY, Thomas, Thomas Zayouna, Thulio Ferraz Assis, Timothe Peignier, Timothy Klim, Tobi, Tomas Volf, Tom Cnops, Tom de Goede, Torgil Svensson, Trustin Lee, Ulf Adams, Ulf Adams, Ulrik Falklof, Uri Baghin, Vaidas Pilkauskas, vardaro, Vasilios Pantazopoulos, Vertexwahn, Vladimir Tagakov, Waleed Khan, William Muir, wisechengyi, Wren Turkal, Xavier Bonaventura, Xdng Yng, Xiangquan Xiao, Yannic Bonenberger, Yannic Bonenberger, Yannic, Yannic, Yesudeep Mangalapilly, Yi Cheng, Yury Evtikhov, Yuval Kaplan, Yuval K, Yuval, yuzhy8701, Zhongpeng Lin, [zqzzq].

Baseline: 0a47a1f Incompatible changes: - Removing java_common.javac_jar Starlark call. - native.existing_rule now returns select values in a form that is accepted by rule instantiation. This is a breaking API change because there is some code that relies on the precise type returned, including brittle workarounds for this bug specifically and insufficiently flexible workarounds for other issues with the intersection of select and native.existing_rule. - flipped incompatible_use_toolchain_resolution_for_java_rules, see bazelbuild#7849 - Query output=xml/proto/location for source files will now show the location of line 1 of the source file (as the new default) instead of its location in the BUILD file. - Specifying a target pattern underneath a directory specified by .bazelignore will now emit a warning, not an error. - Query `--order_output=auto` will now sort lexicographically. However, when `somepath` is used as a top level function (e.g. `query 'somepath(a, b)'`), it will continue to output in dependency order. If you do not want the lexicographical output ordering, specify another `--order_output` value (`no`, `deps` or `full`) based on what ordering you require. - In the build event stream, BuildMetrics.TargetMetrics.targets_loaded is no longer populated. Its value was always mostly meaningless. BuildMetrics.TargetMetrics.targets_configured and BuildMetrics.ActionSummary.actions_created now include configured aspect data. - //visibility:legacy_public has been removed. - Flip and remove incompatible_dont_collect_so_artifacts (bazelbuild#13043). - Remove flag --experimental_no_product_name_out_symlink: it is always true. - The Starlark method generate_dsym in objc fragment has been deleted. Please use the equivalent apple_generate_dsym in cpp fragment instead. - Native libraries in data attribute are not collected. See bazelbuild#13550 for details - Enforce the `--profile` path to be absolute. - Enforce the --memory_profile path to be absolute. - JavaToolchainInfo.jvm_opt returns Depset instead of a list. - --apple_sdk has been deleted. It is a no-op. - --bep_publish_used_heap_size_post_build is now a no-op and will be deleted in a future release. Use --memory_profile=/dev/null instead. - Flipped --incompatible_disallow_resource_jars (see bazelbuild#13221). - Remove --bep_publish_used_heap_size_post_build - JSON trace profile: rename counter names. - Removed --action_graph from the dump command. - Remove `--{experimental_,}json_trace_compression` option. - Remove `--experimental_profile_cpu_usage`. - flipped --incompatible_java_common_parameters (see bazelbuild#12373) - this incompatible change breaks old instances of http_archive that specified netrc as an absolute path. It is unlikely there are many instances in the wild since the path would refer to a netrc file inside the external repository by absolute path. Migration should be straightforward. - genrule switched to use exec transition instead of host. This can break targets with hardcoded output paths. To avoid using hardcoded paths use make variables, see https://docs.bazel.build/versions/4.2.2/be/make-variables.html#pre defined_label_variables - this incompatible change breaks old instances of http_archive that specified netrc as an absolute path. It is unlikely there are many instances in the wild since... - Error Prone now checks for unused return values of additional methods on `java.lang.Object`, which can be disabled using `--javacopts=-Xep:ReturnValueIgnored:OFF` - Error Prone now checks for unused return values of additional methods on `java.lang.Object`, which can be disabled using `--javacopts=-Xep:ReturnValueIgnored:OFF` - The --incompatible_existing_rules_immutable_view flag has been flipped to true. See bazelbuild#13907 for migration notes. - Split up the C++ archive from the C++ link action and set `CppArchive` as mnemonic. - workspace(managed_directories=) is not available anymore. - --legacy_important_outputs now has a default of false. - --legacy_important_outputs default reverted to true. - objc_library now requires CcInfo in its deps. If this breaks you, add empty CcInfo() to your rule. - Flag --experimental_local_memory_estimate removed. - Added a new flag --incompatible_unambiguous_label_stringification, which causes labels in the main repo to stringify into unambiguous forms starting with an @. See bazelbuild#15916 for more information. - analysis_test moved into testing.analysis_test - Flip incompatible_enable_cc_toolchain_resolution (bazelbuild#7260) - (Rollback) Flip incompatible_enable_cc_toolchain_resolution (bazelbuild#7260) - name parameter is removed from rule call (bazelbuild#16301) - name parameter is removed from rule call (bazelbuild#16301) - name parameter is removed from rule call (bazelbuild#16301) - --incompatible_remote_downloader_send_all_headers is flipped to true. See bazelbuild#16356 for details. - GrpcRemoteDownloader only includes relevant headers instead of sending all credentials. - In package_group's `packages` attribute, the syntax "//..." now refers to all packages in the same repository as the package group, rather than all packages everywhere. The new item "public" can be used instead to obtain the old behavior. In `bazel query --output=proto` (and `--output=xml`), the `packages` attribute now serializes with the leading double slash included (for instance, `//foo/bar/...` instead of `foo/bar/...`). See also bazelbuild#16355, bazelbuild#16323, and bazelbuild#16391. - 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: - Args.add_all and Args.add_joined can now accept closures in map_each if explicitly enabled via allow_closure. - Add `--bes_header` flag to pass extra headers to the BES server. - Support local_repository in Bazel Registry's source.json file - The `aquery` and `cquery` commands now respect the `--query_file` flag just like the `query` command. Important changes: - Flag --incompatible_objc_compile_info_migration is removed. See bazelbuild#10854. - Flag --incompatible_objc_compile_info_migration is removed. See bazelbuild#10854. - Flag --incompatible_objc_compile_info_migration is removed. See bazelbuild#10854. - none PAIR=cmita - The --incompatible_load_python_rules_from_bzl flag is now a no-op. - Filter all (instead of just C++) source files for coverage output according to --instrumentation_filter and --instrument_test_targets. - The `--incompatible_disable_native_apple_binary_rule` flag has been added which disables the native `apple_binary` rule. Users who need to use `apple_binary` directly (if they cannot use one of the more specific Apple rules) should load it from https://github.com/bazelbuild/rules_apple. - The Android rules' --use_singlejar_apkbuilder is now a no-op. SingleJar will always be used to build APKs. - dict.setdefault(key, ...) now fails if dict is frozen, even if it already contains key. This is an incompatible API change. - Flag --incompatible_objc_provider_remove_compile_info is removed. See bazelbuild#11359. - Starlark now permits def statements to be nested (closures). - native.existing_rule now returns select values in a form that is accepted by rule instantiation. This is a breaking API change, though the fallout is expected to be small. - Starlark now supports lambda (anonymous function) expressions. - The "test" and "coverage" commands no longer return 3 when a test action fails because of a system error. Instead, the exit code reflects the type of system error. - The undocumented ctx.expand feature no longer exists. - Make --legacy_dynamic_scheduler a no-op flag. - Multiplex persistent workers can now use the JSON protocol. - native.existing_rule now returns a mutable list, not a tuple, for a list-valued attributes. This is an incompatible API change. - Roll back change to have native.existing_rules use list instead of tuple. - BEP includes test suite expansions. - config_setting now honors `visibility` attribute (and defaults to `//visibility:public`) - Change the MultiArchSplitTransitionProvider to be based on platform type + CPU instead of fixed "ios_" + cpu. - enforce config_setting visibility. See bazelbuild#12932 for details. - add a flag to build v4 signature file - Added _direct_source_jars output group to Java related targets. END_PUBLIC - pkg_deb is no longer part of @bazel_tools//build_defs/pkg:pkg.bzl. Use https://github.com/bazelbuild/rules_pkg/tree/main/pkg instead - Allowing the lipo operations to be conditional in the linkMultiArchBinary API for Apple binaries. Single architecture slices are now returned through AppleBinaryOutput and the Starlark API. - Release restriction for "-" in the package name for Python sources. Now `py_binary` and `py_test` targets can have main source file with "-" in the path. - Users consuming BEP may assume that a `named_set_of_files` event will appear before any event referencing that `named_set` by ID. This allows consumers to process the files for such events (eg. `TargetCompleted`) immediately. - BEP includes all files from successful actions in requested output groups. Previously, an output group's files were excluded if any file in the output group was not produced due to a failing action. Users can expect BEP output to be larger for failed builds. - In BEP, TargetComplete.output_group has a new field `incomplete` indicating that the file_sets field is missing one or more declared artifacts whose generating actions failed. - The flag `--toolchain_resolution_debug` now takes a regex argument, which is used to check which toolchain types should have debug info printed. You may use `.*` as an argument to keep the current behavior of debugging every toolchain type. - Add runfiles.merge_all() for merging a sequence of runfiles objects. - runfiles.merge() and merge_all() now respect --nested_set_depth_limit. If you hit the depth limit because you were calling merge() in a loop, use merge_all() on a sequence of runfiles objects instead. - Bazel will no longer create a bazel-out symlink if --symlink_prefix is specified: the directory pointed to via the bazel-out symlink is accessible via ${symlink_prefix}-out. If this causes problems for you, set --experimental_no_product_name_out_symlink=false in your builds and file an issue. - Updates worker protocol with cancellation fields, and adds experimental_worker_cancellation flag to control cancellation. - Simplify build failure output by always using `NNN arguments`. - trim_test_configuration now defaults to on - Mark genrule.srcs as a source attribute for coverage. - When using --allow_analysis_failures (for example, via bazel-skylib's analysistest with `expect_failure = True`), analysis-time failures in aspect implementation functions will now be propagated and saved in AnalysisFailureInfo, just like analysis-time failures in rules. - cquery --noimplicit_deps now correctly filters out resolved cc_toolchains - Sign apks deterministically. - Make gcov optional in cc_toolchain tools. - If --experimental_prefer_mutual_xcode is passed, Bazel will choose the local default (instead of the newest mutually available version) if it's available both locally and remotely. - Remove java_lite_proto_library.strict_deps attribute. - Generate proguard configurations deterministically. - Adds a new flag, `--incompatible_enable_cc_test_feature` which switches from the use of build variables to the feature of the same name. - Dropped fragile xz support from built in pkg_tar. Users requiring xz compression should switch to bazlebuild/rules_pkg. - If all strategies of one branch (the local or remote execution branch) of the `dynamic` strategy fail to even accept (via the response they give from `canExec`) the action, `dynamic` will now try to see if the other branch can accept it. (Trying to run it and it failing will still cause a failure if it was the first result, this is about strategies claiming they can't even try the action) - Add `disable_annotation_processing` option to `java_common.compile`, which disables any annotation processors passed to `plugins` or in `exported_plugins` of `deps` - Remove obsolete --incompatible_prohibit_aapt1 - The minimum Android build tools version for the Android rules is now 30.0.0 - Adds --experimental_reuse_sandbox_directories flag to reuse already-created non-worker sandboxes with cleanup. - --experimental_force_gc_after_build is deprecated and will be removed soon. Use --bep_publish_used_heap_size_post_build instead - Forward coverage-instrumented files from non-tool dependencies by default. - The used_heap_size_post_build field in BEP is populated when the --memory_profile flag is set - --run_validations defaults to true. - Consider label_keyed_string_dict attributes when gathering instrumented files for coverage. - Remove flag --experimental_forward_instrumented_files_info_by_default, now that this behavior is the default. - When using MemoryProfiler with multiple GCs via the --memory_profile_stable_heap_parameters flag, we do a more precise calculation of heap used at the end of the build. This will generally result in lower values. - --bep_publish_used_heap_size_post_build is deprecated. Use --memory_profile=/dev/null instead. - Disable --all_incompatible_changes flag. - The --all_incompatible_changes flag is now a no-op - The `--toolchain_resolution_debug` flag now accepts regexes matching targets, as well as toolchain types, when choosing what debug messages to print. - Adds --experimental_existing_rules_immutable_view flag to make the native.existing_rule and native.existing_rules functions more efficient by returning immutable, lightweight dict-like view objects instead of mutable dicts. - Add support to length-delimited protos as undeclared output annotations [] - The deprecated "relative_to_caller_repository" parameter has been removed from the Label constructor. - The toolchain transition is now enabled for all toolchains. - incompatible_disable_depset_items is flipped - The --experimental_existing_rules_immutable_view flag has been renamed to --incompatible_existing_rules_immutable_view - Bazel no longer supports Java 8. From this version on, the minimum required JDK is OpenJDK 11. - Deprecate --incompatible_applicable_licenses flag, in preparation for removal in Bazel 6.x. - Treat py_*.srcs_version="PY2" the same as "PY2ONLY". - The Build Event Protocol now contains file digests and sizes along with the file name and URI. - Refactor system suspend event handling. - alias() can now select() directly on constraint_value() - Allow \a \b \f \v escape sequences in Starlark. - Match remote and local xcode version by most granular version. - Adds `--experimental_worker_multiplex_sandboxing` flag that controls whether to sandbox multiplex workers that support it. - provider() has a new parameter: init, a callback for performing pre-processing and validation of field values. Iff this parameter is set, provider() returns a tuple of 2 elements: the usual provider symbol (which, when called, invokes init) and a raw constructor (which bypasses init). - Tests that fail to create or complete their `TestAttemptContinuation` by throwing an `ExecException` will report an `INCOMPLETE` status. Previously, Bazel would fail to report any status for the test attempt. - Fixed an issue where Bazel could erroneously report a test passes in coverage mode without actually running the test. - Include more information about configurations in cquery proto formatted output. This deprecates the configuration field of AnalysisProtosV2.ConfiguredTarget, and adds a new field, configuration_id, to be used instead. - experimental cc_library.implementation_deps inverted to interface_deps - In aquery and cquery proto output, indicate if a configuration is a tool or non-tool configuration. - Include complete configurations in cquery proto output. - experimental cc_library.implementation_deps inverted to interface_deps - Make protocOpts() publicly accessible. - Add some documentation about how configuration information is conveyed in cquery proto output. - Introduces experimental static library linking API under apple_common.link_multi_arch_static_library - Further deprecation and removal of pkg_tar. Stop supporting legacy use of 'files' attribute, where it could be a list of labels instead of a map of paths to labels. - Removed --incompatible_no_build_defs_pkg flag. It never fulfilled its purpose because --all_incompatible_changes would never set it. The last rule it gated (pkg_tar) is scheduled to be removed in Bazel 6.x. - Add coverage configuration fragment, used to expose output_generator label. - Bazel now no longer includes system headers on macOS in coverage reports (bazelbuild#14969). - android_sdk_repository read $ANDROID_SDK_ROOT in addition to $ANDROID_HOME. - The default dexer is now d8. dx can be optionally enabled using: --define=android_dexmerger_tool=dx_dexmerger \ --define=android_incremental_dexing_tool=dx_dexbuilder \ --define=android_standalone_dexing_tool=dx_compat_dx \ --use_workers_with_dexbuilder - Packaging support for deploy JAR embedded JDK files (hermetic Java). - Don't stamp cc_common.link actions for tool dependencies. - Starlark test rules can use the new inherited_environment parameter of testing.TestEnvironment to specify environment variables whose values should be inherited from the shell environment. - Enable merging permissions during Android manifest merging with the --merge_android_manifest_permissions flag. - Allow specialization to work with constraint_values. - Bazel uses the D8 jar from Maven instead of the SDK. - Make ijar / java_import preserve classes with `@kotlin.Metadata` annotations - Switch cc_test implementation to Starlark. Note: cc_test will now link statically when _targeting_ Windows regardless of host platform (rather than always linking statically when Windows is the _host_). - Switch cc_test implementation to Starlark. Note: cc_test will now link statically when _targeting_ Windows regardless of host platform (rather than always linking statically when Windows is the _host_). - Add devtools/build/lib/worker:work_request_handlers to the remote android tools release package. This will be transitively packaged into all_android_tools. - Bazel uses the D8 jar from Maven instead of the SDK. - android_sdk_repository read $ANDROID_SDK_ROOT in addition to $ANDROID_HOME. - Advance android_tools_pkg version to 0.24.0. - Switch cc_test implementation to Starlark. Note: cc_test will now link statically when _targeting_ Windows regardless of host platform (rather than always linking statically when Windows is the _host_). - Bazel uses the D8 jar from Maven instead of the SDK. - "blaze config" now only reports info from the last build. To compare configurations across multiple builds, redirect "blaze config" output to a file and run your favorite diff tool. - The --incompatible_override_toolchain_transition flag is now always set, and will be removed in the future. Thus, --noincompatible_override_toolchain_transition has no effect, and the value of the incompatible_use_toolchain_transition parameter in aspect() and rule() builtins is ignored. - Switch cc_test implementation to Starlark. Note: cc_test will now link statically when _targeting_ Windows regardless of host platform (rather than always linking statically when Windows is the _host_). - Toolchain types may now be optional, in addition to mandatory. See https://bazel.build/docs/toolchains#optional-toolchains for further details. - Add six to deps of has_services=1 py_proto_librarys. - pkg_tar(symlinks) has been removed. Users needing that feature should migrate to @rules_pkg. - Aspects can now define and use exec groups using the same API as rules. - Removed the obsolete --incompatible_applicable_licenses flag. The feature is permanently enabled. - embedded_tools packages R8 desugarer again - Bazel now selects sh path based on execution platform instead of host platform, making it possible to execute sh actions in multiplatform builds. --shell_executable now only applies to actions configured for host. - labels in genquery.scope are no longer configured. - When Bzlmod is enabled, all Bzlmod-generated repos will have an extra '@' prepended to their names. This effectively enables the canonical label literal syntax for Bzlmod-generated repos (`@@canonicalRepoName//pkg:target`; see https://docs.google.com/document/d/1N81qfCa8oskCk5LqTW-LNthy6EBrDo t7bdUsjz6JFC4/edit?usp=sharing). - Exposed `CcSharedLibraryInfo` to Starlark builtins. - Enable --use_top_level_targets_for_symlinks by default. - Singlejar accepts runtime Created-By field - --noincompatible_disable_managed_directories, and with that, workspace(managed_directories=) is not supported anymore. - Bazel supports D8 desugaring, albeit without persistent workers - Remove mtime options from pkg_tar. Users should migrate to @rules_pkg. - Test for experimental multiplexed persistent resource processor. - Added new register_{execution_platforms,toolchains} directives to the MODULE.bazel file, to replace the {execution_platforms,toolchains}_to_register attributes on the module() directive. - The legacy pkg_tar no longer supports the ability to untar and repackage an input tar file (`deps` attribute). Users needed that capability must switch to github.com/bazelbuild/rules_pkg. - `cquery`'s new output mode [`--output=files`](https://bazel.build/docs/cquery#files-output) lists the output files of the targets matching the query. It takes the current value of `--output_groups` into account. - Change singlejar metadata to report Created-By Bazel - Add support for fetching RPC credentials from credential helper. - Revert interface_deps back to implementation_deps after problem reported in. Use `buildozer 'rename deps implementation_deps' //...:%cc_library; buildozer 'rename interface_deps deps' //...:%cc_library` - Fix for desugaring failure on Bazel+Android+Windows build scenario. - D8 is the default desugarer - Migrate main_dex_list_creator to D8 (DX deprecation) - --experimental_enable_bzlmod has been renamed --enable_bzlmod, and still defaults to false. - selects() no longer produce irrelevant duplicate label checks - Adds a dexer output cache to CompatDexBuilder to improve build speed. - Improved error messages when analyzing inline bzl code - Improved error messages when analyzing inline bzl code - The `@bazel_tools//tools/cpp:compiler` flag now has the value `gcc` if the configured compiler is detected to be gcc rather than the generic value `compiler`. A branch for `gcc` may have to be added to `select` statements that do not have a default case that handles gcc appropriately. - The `get_child` method of `path` now accepts an arbitrary number of relative path strings as positional arguments. - SourceManifestAction supports `Action.content` - Add --incompatible_build_transitive_python_runfiles alias. See bazelbuild#16303 - The @bazel_tools//tools/cpp:compiler flag now has the value `clang` for the auto-configured Xcode toolchain rather than the generic value compiler. A branch for `clang` may have to be added to select statements that do not have a default case that handles this toolchain appropriately. - added additional debug message to warn of skipped toolchains during resolution - The deprecated --remote_allow_symlink_upload flag has been removed. Symlinks in local action outputs are always permitted, even with remote caching. Whether they're uploaded as symlinks or as the files/directories they point to is still determined by the --incompatible_remote_symlinks flag. - Added `struct`, `json`, `proto`, and `depset` to the starlark environment of Bazel's cquery (--output=starlark) command - Added three `package_group`-related flags: `--incompatible_package_group_includes_double_slash` (bazelbuild#16391), `--incompatible_package_group_has_public_syntax` (bazelbuild#16355), and `--incompatible_fix_package_group_reporoot_syntax` (bazelbuild#16323). With these flags, `package_group` can now easily specify "all packages", "no packages", and "all packages in the current repo". - Record hermetic packaged JDK modules file size in deploy JAR manifest 'JDK-Lib-Modules-Size' attribute. - .bzl files may now set a visibility to guard what other .bzl and BUILD files may load them. See [...] for more information. - Deletes the --extra_proguard_specs Blaze flag - 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`. - `--experimental_remote_cache_compression` has been renamed to `--remote_cache_compression` - The REPO.bazel and MODULE.bazel files are now also considered workspace boundary markers. This release contains contributions from many people at Google, as well as Adam Azarchs, Adam Lavin, Adam Liddell, Adam Singer, Adam Wolf, Albert Lloveras, Alessandro Patti, Alex Eagle, Alex Eagle, Alex Eagle, Alex Scott, AlexTereshenkov, Alex Torok, Amanda L Martin, Andreas Fuchs, Andreas Herrmann, Andreas Herrmann, Andrew Katson, Andrew Klotz, Andy Hamon, Ankush Goyal, Anthony Pratti, Anthony Ter-Saakov, Ara Nguyen, Artem V. Navrotskiy, Artem Zinnatullin, arunkumar9t2, arun.sampathkumar, aryeh, Ast-x64, Austin Schuh, Benedek Thaler, Benjamin Lee, Benjamin Peterson, Benjamin Peterson, Benjamin Sigonneau, Ben Lee, Bohdan Vanieiev, Bo Zhang, Bo Zhang, Bradley Burns, Brandon Duffany, Brandon Jacklyn, Brentley Jones, Brentley Jones, bromano, Cameron Mulhern, Chad Miller, Charles-Francois Natali, Chirag Ramani, Chris Clearwater, Chris Fredrickson, Christopher Peterson Sauer, Christopher Rydell, Christopher Sauer, ckiffel, Cristian Hancila, crydell-ericsson, Dan Bamikiya, Dan Fleming, Daniel Grunwald, Daniel KT, Daniel McCarney, Daniel Wagner-Hall, Danny Wolf, Dave MacLachlan, Dave Nicponski, David Cummings, David, David Ostrovsky, David Sanderson, Delwin9999, Denys Kurylenko, dhmemi, Dimi Shahbaz, divanorama, dmaclach, Dmitry Ivankov, dorranh, ecngtng, Ed Schouten, Eitan Adler, Elliotte Rusty Harold, Emil Kattainen, erenon, Eric Cousineau, Eric Song, Eric Wendelin, Ethan Steinberg, Ezekiel Warren, Fabian Brandstetter, Fabian Meumertzheim, Fabian Meumertzheim, FaBrand, Fahrzin Hemmati, Fahrzin Hemmati, Felix Ehrenpfort, Finn Ball, floriographygoth, frazze-jobb, Fredrik Medley, Garrett Holmstrom, Gaspare Vitta, Gautam Korlam, George Gensure, George Prekas, gkgoat1, gkorlam, goodspark, Greg Estren, Greg, Greg Magolan, Gregory Fong, Greg Roodt, Grzegorz Lukasik, Grzegorz Lukasik, Halil Sener, Halil Sener, Hannes Kufler, Hao Yuan, homuler, hvadehra, hvd, Igor Nazarenko, Ikko Ashimine, Jack Dai, James Broadhead, James Ma, Jan, Jason Tan, Jay Bazuzi, Jeremy Volkman, Jesse Chan, jheaff1, Jiawen Chen, Joe Lencioni, Joel Jeske, Joel Williamson, Johannes Abt, John Hinnegan, John Laxson, John Laxson, John Millikin, Jonathan Gerrish, Jonathan Schear, Jon Landis, Jon Parise, jonrose-dev, Jon Shea, Jordan, juanchoviedo, Julio Merino, Justus Tumacder, Kaiqin Chen, keertk, Keith Smiley, kekxv, Ken Micklas, Kevin Hogeland, Kevin Lin, Kirill Zabelin, Kiron, Konstantin Erman, Krishna Ersson, Krzysztof Naglik, kshyanashree, Kun-Lu, Lauri Peltonen, Lee Mracek, lihu, Liu Liu, lripoche, Lszl Csomor, Luc Bertrand, Luis Fernando Pino Duque, m, Malte Poll, Marc Zych, Marc Zych, Marek uppa, Mark Karpov, Masoud Koleini, Mathieu Olivari, Matt Clarkson, Matt Mackay, Mauricio Galindo, Max Liu, Maxwell Elliott, Menny Even Danan, menny, Michael Chinen, Michael P. Nitowski, Mikhail Balabin, mohamadk, Mostyn Bramley-Moore, Nathaniel Brough, nathyong, Nick Korostelev, Niek Peeters, Nikolay Shelukhin, Nitesh Anandan, Niyas Sait, Noa Resare, odisseus, Oleh Stolyar, Olek Wojnar, Oliver Lee, Olle Lundberg, Omar Zuniga, Oscar Bonilla, Patrick Balestra, Patrick Balestra, Paul Gschwendtner, Paul Tarjan, Peter Kasting, Peter Mounce, Philipp Schrader, Pras Velagapudi, Qais Patankar, Rabi Shanker Guha, Rahul Butani, Rai, Rajeshwar Reddy T, Red Daly, redwrasse, Rifqi Mulya Fahmi, robincaloudis, Robin Tweedie, Roger Hu, Roman Salvador, ron-stripe, rustberry, Ryan Beasley, Ryan Schmidt, Sagar Pathare, Sahin Yort, Saleem Abdulrasool, samhowes, Samuel Giddins, Sara Adams, Sascha Moecker, Sebastian Olsson, Sergey Tyurin, Severin Strobl, Shuai Zhang, Siddhesh Bhupendra Kuakde, Simon Bjorklen, Simon Mavi Stewart, something_vague, Son Luong Ngoc, Stephan Wolski, Steve Siano, steve-the-bayesian, Steve Vermeulen, Stiopa Koltsov, susinmotion, Sven Tiffe, Takeo Sawada, Tao Wang, tatiana, tbaing, Ted Kaplan, Ted Kaplan, Tetsuo Kiso, Thaler Benedek, Thi Doan, Thi Doan, Thi Don, Thomas Carmet, Thomas Chen, ThomasCJY, Thomas, Thomas Zayouna, Thulio Ferraz Assis, Timothe Peignier, Timothy Klim, Tobi, Tomas Volf, Tom Cnops, Tom de Goede, Torgil Svensson, Trustin Lee, Ulf Adams, Ulf Adams, Ulrik Falklof, Uri Baghin, Vaidas Pilkauskas, vardaro, Vasilios Pantazopoulos, Vertexwahn, Vladimir Tagakov, Waleed Khan, William Muir, wisechengyi, Wren Turkal, Xavier Bonaventura, Xdng Yng, Xiangquan Xiao, Yannic Bonenberger, Yannic Bonenberger, Yannic, Yannic, Yesudeep Mangalapilly, Yi Cheng, Yury Evtikhov, Yuval Kaplan, Yuval K, Yuval, yuzhy8701, Zhongpeng Lin, [zqzzq].

Baseline: e7218d5 Incompatible changes: - In package_group's `packages` attribute, the syntax "//..." now refers to all packages in the same repository as the package group, rather than all packages everywhere. The new item "public" can be used instead to obtain the old behavior. In `bazel query --output=proto` (and `--output=xml`), the `packages` attribute now serializes with the leading double slash included (for instance, `//foo/bar/...` instead of `foo/bar/...`). See also bazelbuild#16355, bazelbuild#16323, and bazelbuild#16391. New features: - Support local_repository in Bazel Registry's source.json file Important changes: - Record hermetic packaged JDK modules file size in deploy JAR manifest 'JDK-Lib-Modules-Size' attribute. - .bzl files may now set a visibility to guard what other .bzl and BUILD files may load them. See [...] for more information. This release contains contributions from many people at Google, as well as Adam Singer, Albert Lloveras, Alex Eagle, Benjamin Lee, Benjamin Peterson, Christopher Rydell, Ed Schouten, Eric Wendelin, Fabian Meumertzheim, Jordan, Keith Smiley, Kirill Zabelin, Son Luong Ngoc, Tetsuo Kiso, Waleed Khan, Xavier Bonaventura, Yannic Bonenberger.

brandjon added P1 I'll work on this now. (Assignee required) incompatible-change Incompatible/breaking change team-Build-Language breaking-change-6.0 Incompatible flags to be flipped in Bazel 6.0 labels Sep 29, 2022

brandjon self-assigned this Sep 29, 2022

meteorcloudy added this to the 6.0.0 release blockers milestone Sep 30, 2022

brandjon mentioned this issue Sep 30, 2022

Delete flag incompatible_package_group_has_public_syntax #16365

Open

lberki mentioned this issue Oct 4, 2022

Feature request: visibility-like capability for bzl files (rules, aspects, and macros) #11261

Closed

brandjon mentioned this issue Oct 5, 2022

incompatible_package_group_includes_double_slash #16391

Closed

brandjon added the migration-ready Incompatible flag is ready for migration with Bazel rolling releases or Bazel@last_green label Oct 6, 2022

meteorcloudy modified the milestones: 6.0.0 release blockers, 6.0.0 nice to have Oct 11, 2022

brandjon mentioned this issue Oct 13, 2022

[Downstream CI test] Flip package_group incompatible flags #16465

Closed

copybara-service bot closed this as completed in e899d85 Oct 18, 2022

meteorcloudy mentioned this issue Dec 9, 2022

Bazel downstream failure: Tensorflow visibility issue tensorflow/tensorflow#58825

Closed

meteorcloudy removed this from the 6.0.0 nice to have milestone Jan 4, 2023

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

incompatible_package_group_has_public_syntax #16355

incompatible_package_group_has_public_syntax #16355

brandjon commented Sep 29, 2022 •

edited

lberki commented Oct 4, 2022

brandjon commented Oct 5, 2022

meteorcloudy commented Oct 7, 2022

meteorcloudy commented Oct 7, 2022

meteorcloudy commented Oct 11, 2022

brandjon commented Oct 12, 2022

brandjon commented Oct 12, 2022 •

edited

brandjon commented Oct 13, 2022

brandjon commented Oct 13, 2022 •

edited

meteorcloudy commented Oct 14, 2022

brandjon commented Oct 17, 2022

incompatible_package_group_has_public_syntax #16355

incompatible_package_group_has_public_syntax #16355

Comments

brandjon commented Sep 29, 2022 • edited

lberki commented Oct 4, 2022

brandjon commented Oct 5, 2022

meteorcloudy commented Oct 7, 2022

meteorcloudy commented Oct 7, 2022

meteorcloudy commented Oct 11, 2022

brandjon commented Oct 12, 2022

brandjon commented Oct 12, 2022 • edited

brandjon commented Oct 13, 2022

brandjon commented Oct 13, 2022 • edited

meteorcloudy commented Oct 14, 2022

brandjon commented Oct 17, 2022

brandjon commented Sep 29, 2022 •

edited

brandjon commented Oct 12, 2022 •

edited

brandjon commented Oct 13, 2022 •

edited