1 Commits

Author SHA1 Message Date
Ignacio Ballesteros
52efde64c0 fix: mark rolling 'release' as pre-release so v1.0.0 shows as latest
All checks were successful
CI / build (push) Successful in 21s
Release / build (push) Successful in 26s
Release / update-rolling-release (push) Successful in 6s
Release / publish-release (push) Successful in 6s
2026-02-17 23:52:51 +01:00

View File

@@ -94,11 +94,11 @@ jobs:
-H "Authorization: token ${GITEA_TOKEN}"
done
# Update the release body to reflect the current version
# Update the release body and ensure it stays marked as pre-release
curl -s -X PATCH "${API_URL}/repos/${REPO}/releases/${RELEASE_ID}" \
-H "Authorization: token ${GITEA_TOKEN}" \
-H "Content-Type: application/json" \
-d "{\"body\": \"Rolling release — always points to the latest update manifest (currently v${VERSION}). Do not delete.\"}"
-d "{\"body\": \"Rolling release — always points to the latest update manifest (currently v${VERSION}). Do not delete.\", \"prerelease\": true}"
else
# Create the rolling release for the first time
@@ -118,7 +118,7 @@ jobs:
\"name\": \"Update Manifest (rolling)\",
\"body\": \"Rolling release — always points to the latest update manifest (currently v${VERSION}). Do not delete.\",
\"draft\": false,
\"prerelease\": false
\"prerelease\": true
}")
RELEASE_ID=$(echo "${RELEASE}" | jq -r '.id')