ci: newest version is GitHub-Latest (drop rolling 'latest')#22
Merged
Conversation
…release The manually-maintained rolling 'latest' release duplicated GitHub's built-in Latest and fought it for the badge (so the newest version was never Latest). Drop the delete/recreate step and mark each mainline release --latest instead; .../releases/latest/download/<asset> now resolves to the newest version. release/* back-ports publish --latest=false so they can't steal Latest from a newer mainline release. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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.
Implements option B: one source of truth for 'latest'.
latestrelease (delete/recreate each push) — it duplicated GitHub's built-in Latest and tug-of-warred the badge, so the newest version was never Latest.--latest;release/*back-ports use--latest=falseso they can't steal Latest from a newer mainline version..../releases/latest/download/<asset>now resolves to the newest version (e.g.v0.1.0).Paired with a one-time cleanup (deleting the existing
latestrelease/tag, which hands the badge tov0.1.0).