Open EdSchouten opened 1 week ago
fmeum
commented
1 week ago I would guess that the same thing happened with 7.3.1 before the release of 7.3.2 as the release branch also misses the release commit: https://github.com/bazelbuild/bazel/commits/release-7.3.1
iancha1992
commented
1 week ago @EdSchouten You're right. It is strange because we have https://github.com/bazelbuild/bazel/commit/7c2350a381a30f50e0fbdd450c699d47561bad67
This is not a big deal. But the release team will look into it. Thanks for letting us know!
cc: @bazelbuild/triage
Description of the bug:
Go to this page:
https://github.com/bazelbuild/bazel/releases/tag/7.3.2
Notice how it links to the following commit:
Click on that commit. Now you end up on this page:
https://github.com/bazelbuild/bazel/commit/56d0e2c64f78a887ce50b2618e57159726a7a208
Notice this spooky banner at the top of the page:
I don't see the same thing for 7.3.1, 7.3.0, etc.
Which category does this issue belong to?
No response
What's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
No response
Which operating system are you running Bazel on?
No response
What is the output of
bazel info release?No response
If
bazel info releasereturnsdevelopment versionor(@non-git), tell us how you built Bazel.No response
What's the output of
git remote get-url origin; git rev-parse HEAD?No response
If this is a regression, please try to identify the Bazel commit where the bug was introduced with bazelisk --bisect.
No response
Have you found anything relevant by searching the web?
No response
Any other information, logs, or outputs that you want to share?
No response