feat: dev and rc tags are not marked as latest release - #10030
Merged
Merged
Conversation
orizi
marked this pull request as ready for review
June 3, 2026 10:38
PR SummaryLow Risk Overview Tags whose ref string includes Reviewed by Cursor Bugbot for commit 89c9860. Bugbot is set up for automated code reviews on this repo. Configure here. |
TomerStarkware
approved these changes
Jun 3, 2026
TomerStarkware
left a comment
Collaborator
There was a problem hiding this comment.
@TomerStarkware reviewed 1 file and all commit messages, and made 1 comment.
Reviewable status:complete! all files reviewed, all discussions resolved (waiting on eytan-starkware).
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
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.

Summary
Adds
prereleaseandmake_latestflags to the GitHub release workflow. Releases withrcin the tag are marked as pre-releases, and only releases that do not containdevorrcin the tag are marked as the latest release.Type of change
Please check one:
Why is this change needed?
Release candidates (
rc) were being published as full stable releases and marked as the latest release, which could mislead users into treating pre-release versions as stable.What was the behavior or documentation before?
All releases, including release candidates and dev builds, were published without any pre-release designation and were all eligible to be marked as the latest release.
What is the behavior or documentation after?
rcare published as pre-releases.devnorrcare marked as the latest release.Related issue or discussion (if any)
N/A
Additional context
N/A