-
Notifications
You must be signed in to change notification settings - Fork 4.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Release 6.4.0 - October 2023 #19035
Comments
Requesting 6.4.0 incorporation of remote fixes with #18959 |
The expected first release candidate date has moved to 9/19/2023. There are 2 release blockers. They are currently WIP to be merged to master before being cherry-picked to release-6.4.0. |
Bazel 6.4.0rc1 is now available for those that want to try it out. You can download it from: Please report regressions to https://github.com/bazelbuild/bazel/issues as soon as possible. |
https://releases.bazel.build/6.4.0/rc1/index.html The font in here looks weird |
It's always been like this. We can look at improving those pages. |
In pre-release, but testing it bazelbuild/bazel#19035
In pre-release, but testing it bazelbuild/bazel#19035 Co-authored-by: bazelcommits <[email protected]>
#19621 - would be great if this could be addressed before 6.4.0 goes live. |
Hi Team, |
@comius Can we include the flag |
Hi everyone, |
Bazel 6.4.0rc2 is now available for those that want to try it out. You can download it from: Please report regressions to https://github.com/bazelbuild/bazel/issues as soon as possible. |
6.4.0 is out:
cc @excitoon @vbatts for updating Scoop and Fedora packages. Thanks. |
I kicked off the build, but it was only successful for F37 (all arches), EPEL8 (all arches), and
EPEL9 (all arches).
Failed on F38 (all arches), F39 (all arches), Fedora rawhide (all
arches), and EPEL7 (all arches).
Logs are here for review: https://copr.fedorainfracloud.org/coprs/vbatts/bazel/build/6550571/
|
Status of Bazel 6.4.0
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.4.0, simply send a PR against the
release-6.4.0
branch.Task list:
The text was updated successfully, but these errors were encountered: