Update channels: stable at 20:00 UTC, Nightly checks every 30 minutes

The daily promotion moves to 20:00 UTC (21:00 in Paris in winter time):
PROMOTE_AT and promote.yml's cron (20:07, retries until 21:37), with the docs
that give the time. A launcher left open on Nightly looks for new releases
every 30 minutes; Stable keeps 4 hours. The launcher README's Settings
screenshot shows the Updates choice.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
Ludovic Marie
2026-10-22 14:57:50 +02:00
parent ea5994a58a
commit aa65c74e0f
11 changed files with 46 additions and 34 deletions
+4 -4
View File
@@ -1,11 +1,11 @@
name: promote
# Beta game releases become stable once a day (docs/release-flow.md, "Channels"): at 19:00 UTC (21:00 in Paris in
# summer time, 20:00 in winter) tools/release_channels.py promotes the newest beta that had been out 6 hours by then,
# Beta game releases become stable once a day (docs/release-flow.md, "Channels"): at 20:00 UTC (21:00 in Paris in
# winter time, 22:00 in summer) tools/release_channels.py promotes the newest beta that had been out 6 hours by then,
# passed its release smoke test and isn't covered by an issue labelled release-blocker. Launchers on the Nightly
# channel install every beta when it is published; Stable gets the day's promotion. The later runs of the evening are
# retries for a run GitHub starts late or skips: they promote the same beta, so stable still moves once.
# By hand, from GitHub's app too (Actions > promote > Run workflow):
# gh workflow run promote -f tag=v0.2.3 # that beta now, without waiting for 19:00
# gh workflow run promote -f tag=v0.2.3 # that beta now, without waiting for 20:00
# gh workflow run promote -f tag=v0.2.3 -f force=true # even blocked or without its smoke test
# gh workflow run promote -f dry_run=true # say what would be promoted
# Holding betas back: label an issue release-blocker. While it is open it holds every beta; closed as completed it
@@ -14,7 +14,7 @@ name: promote
# has stalled" says so; it closes itself after the next promotion.
on:
schedule:
- cron: '7,37 19-20 * * *'
- cron: '7,37 20-21 * * *'
workflow_dispatch:
inputs:
tag: