From c852d4e8ef0f5b48ff5dee158cdfbbdd623fc6b5 Mon Sep 17 00:00:00 2001 From: Bryan Haberberger Date: Thu, 11 Jun 2026 16:31:22 -0500 Subject: [PATCH] Latest matters more than Pre-release (#526) --- .github/workflows/release_main.yaml | 15 ++++++++------- 1 file changed, 8 insertions(+), 7 deletions(-) diff --git a/.github/workflows/release_main.yaml b/.github/workflows/release_main.yaml index ee449dd1..4f27310a 100644 --- a/.github/workflows/release_main.yaml +++ b/.github/workflows/release_main.yaml @@ -104,15 +104,16 @@ jobs: exit 0 fi - # Treat any version carrying a prerelease identifier (e.g. -alpha) as a pre-release. - PRERELEASE_FLAG="" - case "$NEXT" in - *-*) PRERELEASE_FLAG="--prerelease" ;; - esac - + # Publish as the repo's "Latest" release rather than a GitHub + # pre-release. While in early access every promotion is an -alpha, and + # "Latest" is the signal consumers actually follow — so the newest + # promotion must own it. The overall pre-release/early-access state is + # carried by the separate `early-access` tag/release, not by flagging + # each version as a GitHub pre-release. --latest is explicit so the new + # release always takes the badge from the prior one. gh release create "$TAG" \ --target "$GITHUB_SHA" \ --title "$TAG" \ --generate-notes \ - $PRERELEASE_FLAG + --latest echo "Published release $TAG"