Tracking Gutenberg Nightly builds

[bph]

The GitHub workflow via the distribute-nightly repo creates the Gutenberg nightly and reports back in a comment on this issue.

Learn more about Gutenberg Nightly

Try it with WordPress Playground

Starting the July 15 we keep track of all the downloads of the Gutenberg Nightly

To learn more about the workflow on the GitHub repo distribute-nightly

[bph]

✅ Nightly 23.7.20260715 built and distributed. Download · Run log

[bph]

✅ Nightly 23.7.20260716 built and distributed. Download · 💾 16 downloads since previous build · Run log

[bph]

✅ Nightly 23.7.20260717 built and distributed. Download · 💾 113 downloads since previous build · Run log

[bph]

✅ Nightly 23.7.20260718 built and distributed. Download · 💾 60 downloads since previous build · Run log

[bph]

✅ Nightly 23.7.20260719 built and distributed. Download · 💾 126 downloads since previous build · Run log

[bph]

✅ Nightly 23.7.20260720 built and distributed. Download · 💾 69 downloads since previous build · Run log

[bph]

✅ Nightly 23.7.20260721 built and distributed. Download · 💾 121 downloads since previous build · Run log

[bph]

❌ Nightly build failed on 2026-07-21. Run log

[bph]

July 21: a GitHub cron delay + race with your manual run.

Timeline (all UTC, 2026-07-21):

• 07:00 — scheduled trigger should have fired (.github/workflows/nightly.yml:24 → cron: '0 7 * * *')
• 09:20:30 — you triggered it manually (workflow_dispatch, run 29817881044) → ✅ success
• 09:26:52 — GitHub finally dispatched the scheduled run (run 29818311427) — 2h27m late
• 09:33:11 — scheduled run failed on the final git push of the ledger commit

Why the scheduled run was late

GitHub Actions cron schedules are best-effort. During high-load windows on the shared runners, jobs get queued and may fire hours late (or occasionally get dropped entirely). Nothing in your repo caused this — it's platform-side. Your recent move to 07:00 UTC didn't help here because GitHub simply didn't dispatch until 09:26. See incident page on GitHub

Why the late run failed

Both runs did the same "Update download ledger" step. The manual run pushed commit 1145751 (and its ledger commit) to main at ~09:27. When the scheduled run reached its push at 09:33, its local main was behind, so:

[bph]

✅ Nightly 23.7.20260722 built and distributed. Download · 💾 62 downloads since previous build · Run log

[bph]

Recent scheduled starts vs. target 07:00 UTC:

Date	Scheduled start (UTC)	Delay	Result
Jul 22	09:26:52	+2h 27m	✅ success
Jul 21	09:26:52	+2h 27m	❌ failure (ledger push race with manual run at 09:20)
Jul 20	10:12:04	+3h 12m	✅ success
Jul 19	09:04:50	+2h 05m	✅ success
Jul 18	08:48:31	+1h 48m	✅ success
Jul 17	09:10:08	+2h 10m	✅ success

Consistently 2–3 hours late all week — this is GitHub Actions scheduling drift on scheduled workflows, not a repo-side issue.

Note today and yesterday both fired at the exact same second (09:26:52), which is GitHub bucketing scheduled runs into fixed later slots.
So it's not unusual or alarming if the workflow doesn't run at 7 am UTC. Give it some time (2+ hours)

[bph]

✅ Nightly 23.7.20260723 built and distributed. Download · 💾 126 downloads since previous build · Run log

[bph]

✅ Nightly 23.7.20260724 built and distributed. Download · 💾 118 downloads since previous build · Run log