LotusGuild/cinny-desktop
3
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 1 Wiki Activity

ci: concurrency (cancel-in-progress) on the release build
Build Lotus Chat Desktop / prepare (push) Successful in 3s
Details
Build Lotus Chat Desktop / build-windows (push) Successful in 20m45s
Details
Build Lotus Chat Desktop / build-linux (push) Successful in 22m25s
Details
Build Lotus Chat Desktop / update-manifest (push) Successful in 3s
Details

Browse Source 
Continuous "latest" builds track lotus HEAD, so only the newest submodule bump
needs to build. Cancel a superseded in-flight release: rapid lotus pushes would
otherwise queue several ~30-min Tauri builds back-to-back, and build-linux runs
on ubuntu-latest — the same runner pool as cinny web CI — so the queue also
starves web CI/deploys. update-manifest only publishes release.json on full
success, so a cancelled run leaves the last good manifest untouched.

Reviewed by 2 agents (SHIP).

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This commit is contained in:
jared
2026-07-19 22:09:19 -04:00
co-authored by Claude Opus 4.8
parent 93b3d1561e
commit c5461ce8ee
1 changed files with 10 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.gitea/workflows/release.yml
+10
View File
@@ -9,6 +9,16 @@ env:
GITEA_URL: https://code.lotusguild.org
REPO: LotusGuild/cinny-desktop
# Continuous "latest" builds track lotus HEAD, so only the newest submodule bump
# needs to build. Cancel a superseded in-flight release: rapid lotus pushes would
# otherwise queue several ~30-min Tauri builds back-to-back, and build-linux runs
# on ubuntu-latest — the same runner pool as cinny's web CI — so the queue also
# starves web CI/deploys. update-manifest only publishes release.json on full
# success, so a cancelled run leaves the last good manifest untouched.
concurrency:
group: desktop-release-${{ github.ref }}
cancel-in-progress: true
jobs:
prepare:
runs-on: ubuntu-latest