Skip to content

Release: 'Deploy hosted web app' times out on Vercel 'Building...', hosted Nightly falls behind desktop #655

Description

@rynfar

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.

Activity

  1. rynfar commented on Sep 18, 2026

    @rynfar
    CollaboratorAuthor

    Likely root cause found: Vercel is rate-limiting builds for the pylon-code account. On 2026-09-18 around 22:30Z the Vercel preview check on PRs #657 and #658 failed outright with a link to https://vercel.com/pylon-code?upgradeToPro=build-rate-limit. The earlier symptoms fit the same cause: previews sitting on "Vercel is deploying your app" for about 40 minutes, and the release workflow's "Deploy hosted web app" job stuck on Building... until its 10-minute timeout, four times. Many PRs plus several nightly dispatches landed that day. Options: fewer preview builds per PR (skip the marketing preview when nothing under apps/marketing changed), a higher plan, or a longer timeout with a retry for the release deploy.

  2. rynfar commented on Sep 18, 2026

    @rynfar
    CollaboratorAuthor

    Confirmed: after #662, a push to #663 (no changes under apps/marketing, packages/shared or the lockfile) got the Vercel status success | Canceled by Ignored Build Step and the check passed without a build. While the account was still rate-limited the rejection happened before the ignore step could run, which is why the first push after the merge still failed. What remains here is only the release workflow's hosted-app deploy timing out while the quota is exhausted.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions