From 41e6c3eca39afb2794eb7d30cb73c45151f425a1 Mon Sep 17 00:00:00 2001 From: Ludovic Marie <136255825+ludovic111@users.noreply.github.com> Date: Thu, 22 Oct 2026 16:23:59 +0200 Subject: [PATCH] release-flow: #releases shows every Nightly silently, pings only for Stable Co-Authored-By: Claude Opus 5.5 --- docs/release-flow.md | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/docs/release-flow.md b/docs/release-flow.md index 52a9d5596..45365e341 100644 --- a/docs/release-flow.md +++ b/docs/release-flow.md @@ -180,8 +180,10 @@ runs the game: GitHub's runners have neither a GPU worth the name nor the game f - `### Known issues`: the bullets of [docs/known-issues.md](known-issues.md); - thanks to outside contributors, how to install, the disclaimer. -Kira posts every published release in #releases and pings the releases role only when the notes have a -`### New` section. +Kira posts every release in Discord's #releases. A Nightly (a game pre-release) is posted silently: no ping and +Discord's @silent flag, so nobody gets a notification. When the same release becomes Stable it is posted again, and +that post pings the releases role when the notes have a `### New` section (at most once every 6 hours). Launcher +releases post without a ping. ### Channels @@ -193,8 +195,8 @@ Every game release is published as a **beta**, a GitHub pre-release, so GitHub's - **Nightly**: every beta as soon as it is built, many times a day; it can break. "Nightly" is a name, not a schedule. An open launcher looks for releases every 30 minutes on Nightly (4 hours on Stable). Launchers from before 0.2 had a "Beta builds" switch instead; on, it reads as Nightly. -`horizon-server update` installs stable builds (`--version ` takes one by name), and Kira announces a release -when it becomes stable: Discord's #releases only ever shows stable ones. +`horizon-server update` installs stable builds (`--version ` takes one by name). In Discord's #releases every +Nightly is posted silently and only Stable posts notify (above). `.github/workflows/promote.yml` runs `tools/release_channels.py promote` once a day at 20:00 UTC (21:00 in Paris in winter time, 22:00 in summer), with retries until 21:37 for a run GitHub starts late or skips. It promotes the newest