From 3a7f2472f6f67cef19305ea4e2d66d0771a21f1a Mon Sep 17 00:00:00 2001
From: not-compromised <94505409+not-compromised@users.noreply.github.com>
Date: Mon, 12 Oct 2026 08:20:33 -0500
Subject: [PATCH] fix(fork): revive the nightly schedule GitHub dropped

The fork sat untouched from Jul 7 to Sep 30, so GitHub disabled its
schedules on Sep 5 (60 days without activity). The 07:30 UTC nightly
added on Oct 11 never fired. A person's commit that changes the cron
line is what reactivates them, so move it to 07:35.
---
 .github/workflows/fork-nightly.yml | 4 +++-
 FORK.md                            | 4 ++--
 2 files changed, 5 insertions(+), 3 deletions(-)

diff --git a/.github/workflows/fork-nightly.yml b/.github/workflows/fork-nightly.yml
index 43d1d22cd09fe..0a0e4d3d829f0 100644
--- a/.github/workflows/fork-nightly.yml
+++ b/.github/workflows/fork-nightly.yml
@@ -8,7 +8,9 @@ on:
   schedule:
     # Finishes before the owner's 08:30 UTC digest scan, which reports a fork
     # still behind upstream; servers install the release within 30 minutes.
-    - cron: "30 7 * * *"
+    # GitHub drops a public repo's schedules after 60 days without activity
+    # and revives them only when a person commits a change to this line.
+    - cron: "35 7 * * *"
   workflow_dispatch:
     inputs:
       target_tag:
diff --git a/FORK.md b/FORK.md
index 9d89a4ab9ba58..69bfa23194226 100644
--- a/FORK.md
+++ b/FORK.md
@@ -32,7 +32,7 @@ nightly.
 
 ## Nightly pipeline
 
-`.github/workflows/fork-nightly.yml` runs daily at 07:30 UTC and on demand.
+`.github/workflows/fork-nightly.yml` runs daily at 07:35 UTC and on demand.
 
 1. It picks the newest upstream nightly release tag.
 2. It refuses to ship by itself if `ORCHESTRATION_PROTOCOL_VERSION` changed,
@@ -124,7 +124,7 @@ otherwise.
 
 - **Commits:** `chore(fork): nightly rolling rebase and release pipeline`
 - **Must still be true:**
-  - Daily at 07:30 UTC and on demand, the newest upstream nightly gets
+  - Daily at 07:35 UTC and on demand, the newest upstream nightly gets
     `custom` replayed onto it, checked and built; it ships only when every
     step is green.
   - A changed `ORCHESTRATION_PROTOCOL_VERSION` never ships without