Skip to content

ci: reduce release polling cron to daily at 04:17 UTC - #15

Merged
rlauuzo merged 1 commit into
masterfrom
capy/ci-reduce-release-polling
Jul 17, 2026
Merged

rlauuzo merged 1 commit into
masterfrom
capy/ci-reduce-release-polling

Conversation

@rlauuzo

@rlauuzo rlauuzo commented Jul 17, 2026 •

Copy link
Copy Markdown
Member

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 */30 cron 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 UTC
  • Urgent releases remain available on demand via workflow_dispatch (with force_release if the upstream SHA hasn't changed), which also forwards to the 12.0 branch via the dispatch-jellyfin-12 job

Open in Capy

Summary by Sourcery

CI:

  • Update release workflow cron expression to reduce upstream polling frequency to a single daily run at 04:17 UTC.

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
@rlauuzo rlauuzo added the capy Generated by capy.ai label Jul 17, 2026 — with Capy AI
@sourcery-ai

sourcery-ai Bot commented Jul 17, 2026 •

Copy link
Copy Markdown
Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

This 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 scheduling

sequenceDiagram
    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
Loading

File-Level Changes

Change Details Files
Adjust release workflow schedule to run once daily at a specific off-peak time instead of every 30 minutes.
  • Updated the GitHub Actions schedule trigger cron expression from a 30-minute interval to a single daily run at 04:17 UTC.
  • Retained existing repository_dispatch triggers for urgent or manual releases without modification.
.github/workflows/release.yml

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

@sourcery-ai sourcery-ai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey - I've reviewed your changes and they look great!


Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

@kilo-code-bot

kilo-code-bot Bot commented Jul 17, 2026 •

Copy link
Copy Markdown

Code Review Summary

Status: No Issues Found | Recommendation: Merge

Overview

Severity Count
CRITICAL 0
WARNING 0
SUGGESTION 0
Files Reviewed (1 file)
  • .github/workflows/release.yml - Cron expression change only; no issues found

Notes

This PR modifies only .github/workflows/release.yml, changing the scheduled release polling from every 30 minutes to daily at 04:17 UTC. No C#/.NET source files were touched, so the requested .NET/C# design pattern review criteria do not apply to this change. The cron expression 17 4 * * * is syntactically valid and aligns with the PR description's intent.

Fix these issues in Kilo Cloud


Reviewed by step-3.7-flash · Input: 37.4K · Output: 2.4K · Cached: 115.2K

@rlauuzo
rlauuzo merged commit 0b27b48 into master Jul 17, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

capy Generated by capy.ai

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant