ci: The latest tag follows the newest version tag

When v$VERSION is released, move the latest tag and release to it and replace its bundle, so the older install URL keeps giving the newest version.
This commit is contained in:
theupriser committed 2026-09-24 10:09:26 +02:00
1 parent b2858d3d60
commit b306a72255
4 files changed
+26 -6

No files matched your search

+15 -1
View File
@@ -1,8 +1,10 @@
# Builds the single-file wizard (.github/tools/bundle.sh) and publishes it as a
# release per version: tag v$VERSION (VERSION in setup-gamescope-boot.sh),
# with that version's CHANGELOG.md section as notes. A released version is
# never overwritten; the newest one is marked latest, so this always gets it:
# never overwritten; the newest one is marked latest, and the "latest" tag and
# release are moved to it, so both of these always get the newest version:
# curl -fsSL https://github.com/theupriser/cachyos-gamescope-boot/releases/latest/download/setup-gamescope-boot.sh | bash
# curl -fsSL https://github.com/theupriser/cachyos-gamescope-boot/releases/download/latest/setup-gamescope-boot.sh | bash
# Pull requests only build and check it, and warn when VERSION is already released.
name: Single-file build
@@ -72,3 +74,15 @@ jobs:
$changes"
gh release create "v$VERSION" dist/setup-gamescope-boot.sh \
--target "$GITHUB_SHA" --title "v$VERSION" --notes "$notes" --latest
# "latest" follows the newest version tag, for the older install URL
# (.../releases/download/latest/...). Only moved when a new version
# is released, never for a push without a VERSION bump.
git tag -f latest "$GITHUB_SHA" && git push -f origin latest
latest_notes="Always the newest version, currently v$VERSION (see its release for the changes)."
if gh release view latest >/dev/null 2>&1; then
gh release edit latest --title "Latest (v$VERSION)" --notes "$latest_notes" --latest=false
else
gh release create latest --title "Latest (v$VERSION)" --notes "$latest_notes" --latest=false
fi
gh release upload latest dist/setup-gamescope-boot.sh --clobber