Release 5.1 - March 2022

[Wyverald]

Status of Bazel 5.1

• Expected release date: 2022-03-24
• Release blockers milestone

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.1, simply send a PR against the release-5.1.0 branch.

Task list:

• Create draft release announcement
• Send for review the release announcement PR: add blog post for 5.1 bazel-blog#271
• Push the release, notify package maintainers:
• Update the documentation
• Push the blog post
• Update the release page

[martis42]

Please cherry-pick this fix #14646 (comment)

[comius]

Please cherry-pick 0e73219

[sgammon]

We humbly request #14724 be added to unblock coverage in rules_apple

[Wyverald]

Please cherry-pick 0e73219

@comius could you send a cherry-pick PR against release-5.1.0? This commit doesn't look trivial to cherry-pick.

[comius]

@comius could you send a cherry-pick PR against release-5.1.0? This commit doesn't look trivial to cherry-pick.

Done:
#14952

[sluongng]

As discussed in #13879 (comment) I just opened #14959

Hoping that it can be picked to 5.1 if possible 🙇‍♂️

Edit: now that the PR is merged, the commit is b1bf9d6

[Wyverald]

Status update: there are still a few rather key release blockers (a couple internal ones too), so we'll have to postpone the release again.

[linzhp]

Can you cherry-pick f421474 and a6c3f23?

[kmicklas]

Any chance we can get f9882e4 cherry-picked?

[Wyverald]

Thank you so much, @brentleyjones!

@linzhp @kmicklas For future reference, please send a cherry-pick PR against the branch release-5.1.0. It's much easier to keep track of PRs than comments in this issue.

[Wyverald]

5.1 is now out!

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