ci: reduce release polling cron to daily at 04:17 UTC - #15
Conversation
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
Reviewer's guide (collapsed on small PRs)Reviewer's GuideThis PR adjusts the release GitHub Actions workflow to poll upstream once per day at 04:17 UTC instead of every 30 minutes, aligning with downstream manifest update timing and reducing unnecessary churn while preserving manual trigger support. Sequence diagram for updated release workflow schedulingsequenceDiagram
participant GitHubCron as GitHub_schedule_17_4_UTC
participant ReleaseWorkflow as Release_workflow_release_yml
participant ManifestCron as Manifest_repo_cron_06_UTC
actor Maintainer
GitHubCron->>ReleaseWorkflow: run release workflow (daily 17 4 * * *)
ReleaseWorkflow->>ManifestCron: publish updated release before 06:00 UTC
Maintainer->>ReleaseWorkflow: workflow_dispatch (force_release)
ReleaseWorkflow->>ManifestCron: publish urgent release before next scan
File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
Code Review SummaryStatus: No Issues Found | Recommendation: Merge Overview
Files Reviewed (1 file)
NotesThis PR modifies only Fix these issues in Kilo Cloud Reviewed by step-3.7-flash · Input: 37.4K · Output: 2.4K · Cached: 115.2K |
Reduces the release workflow's upstream polling from every 30 minutes to once daily. Catalog delivery is already gated by the manifest repository's daily 06:00 UTC update cron, so sub-daily release polling added churn (several tags per day rotating the manifest's 5-version window) without getting updates to users any faster. Daily polling batches a whole day's segment-editor changes into one release.
17 4 * * *rather than a top-of-the-hour slot: GitHub deprioritizes scheduled runs at high-load times (the old*/30cron actually fired every 1–2.5 hours), and 04:17 leaves a >1.5h buffer for the release to publish before the manifest cron scans at 06:00 UTCworkflow_dispatch(withforce_releaseif the upstream SHA hasn't changed), which also forwards to the 12.0 branch via thedispatch-jellyfin-12jobSummary by Sourcery
CI: