[9.2.0] Fix: Prevent GitHub 'Latest' badge regression on maintenance releases…#29541
Merged
Merged
Conversation
…bazelbuild#29452) Problem: GitHub automatically marks the most recently created release as "Latest." When a maintenance patch (e.g., 8.7.0) is released after a newer major version (e.g., 9.1.0), the "Latest" badge incorrectly regresses to the older version. Solution: Updated scripts/ci/build.sh to perform a semantic version check using sort -V. If the new release is semantically older than an existing one, the script now explicitly calls the GitHub API to set make_latest: false, ensuring the badge stays on the true highest version. Impact: - Guarantees the "Latest" badge always points to the highest semantic version. - Prevents legacy branch updates from hijacking the project's "Latest" status. - Syncs GitHub UI state with the fix introduced in bazelbuild/continuous-integration#2598. PR #[2598](bazelbuild/continuous-integration#2598) (Continuous-integration): Fixes the Docker Registry (bazel:latest tag). PR bazelbuild#29452 (Bazel): Fixes the GitHub Releases Page (the green "Latest" badge). PR #[2692](bazelbuild/continuous-integration#2602) (Continuous-integration): Buildkite pipeline for Github CLI migration. Closes bazelbuild#29452. PiperOrigin-RevId: 914121481 Change-Id: Ic725b3e49105b3d25c54545740e289a6f13f1aa0
iancha1992
added
team-OSS
Wyverald
approved these changes
May 14, 2026
Merged
via the queue into
bazelbuild:release-9.2.0
with commit May 14, 2026
c67c060
46 checks passed
github-actions
Bot
removed
the
awaiting-review
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
… (#29452)
Problem:
GitHub automatically marks the most recently created release as "Latest." When a maintenance patch (e.g., 8.7.0) is released after a newer major version (e.g., 9.1.0), the "Latest" badge incorrectly regresses to the older version.
Solution:
Updated scripts/ci/build.sh to perform a semantic version check using sort -V. If the new release is semantically older than an existing one, the script now explicitly calls the GitHub API to set make_latest: false, ensuring the badge stays on the true highest version.
Impact:
PR #2598 (Continuous-integration): Fixes the Docker Registry (bazel:latest tag).
PR #29452 (Bazel): Fixes the GitHub Releases Page (the green "Latest" badge).
PR #2692 (Continuous-integration): Buildkite pipeline for Github CLI migration.
Closes #29452.
PiperOrigin-RevId: 914121481
Change-Id: Ic725b3e49105b3d25c54545740e289a6f13f1aa0
Description
Motivation
Build API Changes
No
Checklist
Release Notes
RELNOTES: None
Commit a49b777