From e8c3d775aa0a25f4ae444ad2e923112ae5cdb403 Mon Sep 17 00:00:00 2001 From: agw Date: Wed, 30 Sep 2026 22:15:00 +0200 Subject: [PATCH] Run the scheduled build in the evening The AUR push is made under the maintainer's name and should land in the evening rather than during working hours. At 16:00 UTC a two-hour build publishes around 19:00-20:30 local time. Claude-Session: https://claude.ai/code/session_01GGe7kUhooMFuzY6GaDb2w9 --- .gitea/workflows/build.yml | 5 ++++- README.md | 2 +- 2 files changed, 5 insertions(+), 2 deletions(-) diff --git a/.gitea/workflows/build.yml b/.gitea/workflows/build.yml index b1a0fba..aa7b153 100644 --- a/.gitea/workflows/build.yml +++ b/.gitea/workflows/build.yml @@ -7,7 +7,10 @@ name: Build JASP binary and publish to AUR on: schedule: - - cron: '0 3 * * *' + # 16:00 UTC is 18:00 CEST / 17:00 CET. A full build takes a little over two + # hours, so the AUR push (made under the maintainer's name) and the + # state.json commit land on an evening, not in working hours. + - cron: '0 16 * * *' workflow_dispatch: inputs: jasp_tag: diff --git a/README.md b/README.md index 3239c45..76e13f3 100644 --- a/README.md +++ b/README.md @@ -73,7 +73,7 @@ ships 2.0.0 — so the build compiles those itself, matching what upstream CI do ## Flow ``` -nightly (03:00) ─► check-upstream.py +daily (16:00 UTC) ─► check-upstream.py │ new JASP tag, or a Qt major transition? ▼ build-jasp.sh (Arch container, hours)