Release 6.3.0 - July 2023

[iancha1992]

Status of Bazel 6.3.0

• Expected first release candidate date: 2023-07-13
• Expected release date: 2023-07-24
• 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 6.3.0, simply send a PR against the release-6.3.0 branch.

Task list:

• Create release candidate
• Check downstream projects
• Create draft release announcement
• Push the release and notify package maintainers
• Update the documentation
• Update the release page

[keertk]

RC1 has been postponed by a week (new date 7/12 7/13) since there are quite a few issues that are still being worked on.

We'll continue to post here if there are any further changes to the schedule.

[iancha1992]

Bazel 6.3.0rc1 is now available for those that want to try it out.

You can download it from:
https://releases.bazel.build/6.3.0/rc1/index.html

Please report regressions to https://github.com/bazelbuild/bazel/issues as soon as possible.

[jsharpe]

#18936 affects this release.

[werkt]

Requesting a block of commits to be merged from remote: #18959

[Wyverald]

6.3.0rc1 is already out, and we can't cherry-pick anything other than regression fixes etc at this point. Your changes will need to wait until 6.4.0.

[brentleyjones]

(I'm glad to hear that 6.4.0 is confirmed.)

[werkt]

6.3.0rc1 is already out, and we can't cherry-pick anything other than regression fixes etc at this point. Your changes will need to wait until 6.4.0.

Alright, I'll pay attention to 6.4.0 news when it comes out, Thanks for the heads up.

[iancha1992]

Bazel 6.3.0rc2 is now available for those that want to try it out.

You can download it from:
https://releases.bazel.build/6.3.0/rc2/index.html

Please report regressions to https://github.com/bazelbuild/bazel/issues as soon as possible.

[fmeum]

@iancha1992 In an offline discussion, @Wyverald expressed concerns about the complexity introduced by the isolate parameter of use_extension. Since it is not too late to guard it with an experiment flag, but would be after the 6.3.0 release, we should wait for his confirmation.

[iancha1992]

6.3.0 is out:

• https://github.com/bazelbuild/bazel/releases/tag/6.3.0
• https://releases.bazel.build/6.3.0/release/index.html

cc @excitoon @vbatts for updating Scoop and Fedora packages. Thanks.

[vbatts]

would someone like to try their hand at building the rpms for fedora? I will not be able to do this.

[keertk]

@vbatts could you share the steps to do this?

[vbatts]

https://github.com/vbatts/copr-build-bazel has the build steps. The version number in the bazel.spec is usually what gets bumped. But currently it likely needs a patch, which could be added similar to the existing 1354.patch file. Once `make .container.rebuild` works for building the new version, it can be pushed to copr. Currently only I have rights to do that, but maybe can share that with someone in the future.

[keertk]

Ok, thanks for the info! We'll take a look and get back to you.

[vbatts]

On 25/07/23 09:34 -0700, keertk wrote: Ok, thanks for the info! We'll take a look and get back to you.

I've just looked into this lightly. There is a build of bazel v6.3.1 for fedora 37, but fedora 38 fails with a new error.

[meteorcloudy]

@vbatts Thanks for maintaining the fedora build and looking into the issue! Unfortunately, the Bazel team doesn't have capacity to look into this right now since we don't maintain the package for fedora officially. But if you figure out a fix, we'll be very happy to accept a PR!