Merge release workflow into the main build workflow

build-release.yml and build-main.yml ran identical steps (checkout, node, npm install, npm run build, make appstore) and differed only in where the package landed. Fold the v* tag trigger into build-main.yml and branch on gitea.ref in the publishing step: main keeps the rolling latest-main pre-release, tags get a normal release on the tag that was just pushed. Tag deletion is now guarded - only latest-main is recreated, since deleting a version tag would destroy the ref that triggered the run. A stale release is still removed in both cases so moved tags republish cleanly. Side effects: version builds are published as durable release assets with a stable URL instead of expiring workflow artifacts, which drops the last actions/upload-artifact usage and with it the @v3 pin forced by the GHES restriction; and the setup-php step goes away, since make appstore only shells out to mkdir/tar/rm.
2026-08-13 13:46:34 +02:00
parent d2f6640d3d
commit e06e382147
4 changed files with 54 additions and 59 deletions
@@ -80,7 +80,7 @@ In [`.gitea/workflows/`](.gitea/workflows/):
 | `lint-php.yml` | `php -l` über eine PHP-8.2–8.4-Matrix |
 | `lint-info-xml.yml` | validiert `appinfo/info.xml` gegen das Appstore-XML-Schema |
 | `phpunit.yml` | führt die PHPUnit-Tests aus (SQLite/rein logisch, kein DB-Service nötig) |
-| `build-release.yml` | baut bei Push eines `v*`-Tags das Frontend und paketiert das Appstore-Archiv |
+| `build-main.yml` | baut Frontend + Appstore-Archiv und veröffentlicht es als Release-Asset — bei Push auf `main` als rollendes Pre-Release `latest-main`, bei Push eines `v*`-Tags als reguläres Release |

 ## Datenmodell