fix(ci): keep the repository-wide latest badge on the CLI release#5997
Merged
Conversation
release-desktop.yml's header reserves GitHub's repository-wide "latest" for the CLI line, but gh release create was not passing --latest=false, so whichever line published second won the badge — desktop-v1.17.0 stole it this cycle (fixed by hand with gh release edit). Pin desktop releases to --latest=false so the badge stays on the v* line.
github-actions
Bot
added
v2
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
1 participant
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.
Problem
release-desktop.yml's own header says GitHub's repository-wide latest badge is reserved for the CLI (v*) line, butgh release createnever passed--latest=false— so whichever line publishes second wins the badge. In the 1.17.0 cycle the desktop pipeline finished after the CLI one anddesktop-v1.17.0stolelatest(corrected by hand withgh release edit v1.17.0 --latest).Fix
Pin desktop stable releases to
--latest=falseso the badge stays on thev*line regardless of publish order. Canary is unaffected (no GitHub release), and prereleases were already excluded fromlatestby--prerelease.Verification
actionlintpasses.gh release create --latest=falseverified against gh CLI docs; runtime path exercises on the nextdesktop-v*tag.🤖 Generated with Claude Code