Repository navigation
Release pipeline: publish suffixed tags (betas, RCs) as GitHub pre-releases - #8710
Merged
Aaronontheweb merged 1 commit intoOct 2, 2026
Merged
Conversation
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.
Purpose
The 1.6.0-beta1 GitHub release was created as a full release, so GitHub marked it "Latest" ahead of 1.5.71. I fixed that by hand. This makes the release pipeline do it automatically.
Change
build-system/windows-release.yaml: a runtime variableisPreReleaseis true when the tag name contains-(1.6.0-beta1,1.6.0-rc1), andGitHubRelease@0passes it asisPreRelease. Stable tags like1.5.72are unchanged. GitHub never marks a pre-release as "Latest".Verification
The YAML parses. This pipeline only runs on tag pushes, so PR validation doesn't exercise it; the next beta or RC tag is the first real run.
Breaking changes
None.