What happens
The release workflow's Deploy hosted web app job is cancelled at its 10-minute timeout while the Vercel CLI prints Building.... It happened four times in a row on 2026-09-18:
- run 35387661237 (nightly
.201): first attempt and two --failed re-runs, 20:08Z, 20:19Z, 20:59Z
- run 35395816639 (nightly
.204): 21:3xZ
The same job succeeded on run 35379218634 at about 18:30Z the same day. The desktop builds, the GitHub release and the updater metadata all succeed each time, so desktop Nightly is unaffected; the hosted web Nightly channel stays on the last build that deployed (.200).
During the same window a Vercel preview check for the marketing site sat on "Vercel is deploying your app" for about 40 minutes on an unrelated PR before passing, so Vercel-side slowness is likely part of it.
What to decide
- Whether the hosted app's Vercel build now simply takes longer than 10 minutes (
timeout-minutes: 10 around line 900 of .github/workflows/release.yml), in which case the timeout needs raising.
- Whether a cancelled deploy should fail the whole run as "cancelled", which makes a published nightly look like it did not publish.
Not investigated inside Vercel; the build logs there will say which.
What happens
The release workflow's Deploy hosted web app job is cancelled at its 10-minute timeout while the Vercel CLI prints
Building.... It happened four times in a row on 2026-09-18:.201): first attempt and two--failedre-runs, 20:08Z, 20:19Z, 20:59Z.204): 21:3xZThe same job succeeded on run 35379218634 at about 18:30Z the same day. The desktop builds, the GitHub release and the updater metadata all succeed each time, so desktop Nightly is unaffected; the hosted web Nightly channel stays on the last build that deployed (
.200).During the same window a Vercel preview check for the marketing site sat on "Vercel is deploying your app" for about 40 minutes on an unrelated PR before passing, so Vercel-side slowness is likely part of it.
What to decide
timeout-minutes: 10around line 900 of.github/workflows/release.yml), in which case the timeout needs raising.Not investigated inside Vercel; the build logs there will say which.