Release 5.2 - April 2022

[ckolli5]

Status of Bazel 5.2

• Expected release date: 2022-06-07
• List of release blockers

To report a release-blocking bug, please add a comment with the text @bazel-io flag to the issue. A release manager will triage it and add it to the milestone.

To cherry-pick a mainline commit into 5.2, simply send a PR against the release-5.2.0 branch.

Task list:

• Create draft release announcement
• Send for review the release announcement PR:
• Push the release, notify package maintainers:
• Update the documentation
• Push the blog post
• Update the release page

[foxandi]

Is it possible to get #15306 into this release and have an updated/regenerated embedded JDK for Windows? If yes, I will create a PR with the change against the release branch.

[Wyverald]

Should be possible. I'm not entirely sure what updating the embedded JDK entails; @hvadehra @comius to comment

[foxandi]

Thanks :) I created the PR: #15342

[linzhp]

Can you also include #15341?

[AustinSchuh]

I'm unable to run our tests on a remote execution cluster with 5.2.

The description from @TLATER on the following ticket describes exactly the symptoms I'm seeing, and reverting the patch he mentions fixes it for me. #12821 Can we get 0080572 reverted, or the C++ rules fixed?

[nkoroste]

Can we include the following Android correctness, stability and performance improvements:

1. Support uses-permission merging in manifest merger #13445
2. Zipalign the incremental APK before install #13653
3. Zipalign the split APK before installing #13718
4. Make AndroidCompiledResourceMergingAction worker compatible #14424
5. Avoid leaking Aapt2ResourcePackagingAction args between requests #14425
6. Improve CompatDexBuilder worker compatibility #14430
7. Remove duplicate ManifestProcessingException #14613

Non of them are breaking changes.

cc @Bencodes @ahumesky

[nkoroste]

Can we also include:

1. 1db39e0
2. Add target label to SpawnExec in the execution log #14818

It adds target label to SpawnExec in the execution log that helps with debugging.

[AustinSchuh]

I'm still unable to run our tests with bazel 5.2.0rc1, which is blocking us from upgrading from bazel 5.0. This looks like a regression in how cc_test, external repositories, and remote execution interact. The suggested fix in to add linkstatic = 1 to every cc_test, which is an incompatible change. The discussion on #12821 has stalled. Reverting 0080572 continues to fix the problem. Could we get a revert cherry-picked, or the C++ rules fixed?

[ckolli5]

5.2 is now out!

@vbatts @petemounce @excitoon Could you please update relevant package managers? Thanks!

[Wyverald]

@ckolli5 could you update the release page to point to the release notes blog post? (see last item in the checklist at the top of this page) Then this issue can be closed.

[Mizux]

Concerning Fedora:latest aka 36, there is currently compilation issue please take a look at:

• No bazel5 on fedora:36 (and fedora:latest) vbatts/copr-build-bazel#18

note: At Bazel Team Googlers / Fedora Community, few words from vbatts:

also, yes I need to hand over maintainership on the fedora builds

ref: vbatts/copr-build-bazel#18 (comment)