Move the weekly release off the top of the hour

The 09:00 UTC schedule competes for GitHub's busiest slot. The first
scheduled run started almost six hours late, and on 2026-09-14 no run had
started four and a half hours in, so that week was cut by hand. 09:17 is
still best-effort, but no longer queues behind every on-the-hour schedule.
This commit is contained in:
2026-09-14 06:40:07 -07:00
parent 1dc0caeae9
commit e1f0904184
+14 -6
View File
@@ -13,13 +13,21 @@ name: Weekly release
on: on:
schedule: schedule:
# Mondays, 09:00 UTC. GitHub runs scheduled jobs on a best-effort basis and # Mondays, 09:17 UTC. GitHub runs scheduled jobs on a best-effort basis and
# can delay a run by a good while when the queue is busy, so do not read # can delay a run by a good while when the queue is busy, so do not read
# the exact minute as a promise. Note also that GitHub disables scheduled # the exact minute as a promise. The odd minute is deliberate: the top of
# workflows in a repository with no activity for 60 days -- not a concern # the hour is when most schedules fire, and at 09:00 the first scheduled
# while this one is being worked on weekly, but it is why a silent stop is # run started almost six hours late and the second had not started at all
# worth checking for before assuming the file is broken. # four and a half hours in. Moving off the hour does not make GitHub keep
- cron: "0 9 * * 1" # time, but it stops competing for the busiest slot. A missed week can be
# cut by hand with workflow_dispatch; a late scheduled run that follows
# finds the tag already there and does nothing.
#
# Note also that GitHub disables scheduled workflows in a repository with
# no activity for 60 days -- not a concern while this one is being worked
# on weekly, but it is why a silent stop is worth checking for before
# assuming the file is broken.
- cron: "17 9 * * 1"
workflow_dispatch: workflow_dispatch:
inputs: inputs:
dry_run: dry_run: