6 Commits

Include renames

Author	SHA1	Message	Date
Patrick Niebeling	e06e382147	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
Patrick Niebeling	c5bf6f8f0d	Add rolling main-branch build workflow for manual server deploys ... Publishes the appstore package as a Gitea release asset on every push to main, so a deployable build can be grabbed without cutting a version tag first.	2026-08-13 12:52:29 +02:00
Patrick Niebeling	086c8c06f3	Pin actions/upload-artifact back to v3 ... v4+ uses the @actions/artifact v2 backend, which this self-hosted Gitea instance rejects as unsupported since it identifies as GHES to the action's GHES-detection check. checkout/setup-node don't have this issue and stay on v7.	2026-08-13 12:13:52 +02:00
Patrick Niebeling	d4c75c4942	Bump pipeline actions to latest major versions ... actions/checkout v4 -> v7, actions/setup-node v4 -> v7, actions/upload-artifact v4 -> v7 across all workflows. shivammathur/setup-php stays on the floating @v2 tag, which already resolves to the latest 2.x release.	2026-08-13 12:06:26 +02:00
Patrick Niebeling	e5f02f3bcc	Fix build-release.yml: use npm install, not npm ci ... No package-lock.json is committed (intentionally gitignored), so npm ci has nothing to install from and fails with EUSAGE.	2026-08-13 10:34:55 +02:00
Patrick NiebelingandClaude Sonnet 5	300acde27e	Add Deck workflow automation Nextcloud app ... Ports the standalone due-date cron script into a proper Nextcloud 34 app with a personal-settings UI, per-user workflow configuration (source/target stack, assigned-user and label filters, email notification), a TimedJob background runner, and Gitea CI pipelines. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-08-13 10:13:05 +02:00