Skip to content

ci: Release Smoke gets 20 minutes, so a lockfile change doesn't time it out - #954

Merged
badcuban merged 1 commit into
mainfrom
ci/release-smoke-timeout
Nov 16, 2026
Merged

badcuban merged 1 commit into
mainfrom
ci/release-smoke-timeout

Conversation

@badcuban

Copy link
Copy Markdown
Collaborator

A lockfile change cold-starts the Vite+ cache. On #950, "Setup Vite+" alone took about 8 minutes, and the 10-minute cap cancelled Release Smoke while it was saving the cache, after the smoke checks had already passed. A re-run with a warm cache took under 2 minutes.

The cap goes to 20 minutes, which leaves room on a slow runner. Checks and Build got 30 minutes for the same reason. A normal run still takes 1–2 minutes.

…it out

A lockfile change cold-starts the Vite+ cache. On #950, setup alone took
about 8 minutes and the 10-minute cap cancelled the job while it saved the
cache, after the smoke checks had passed.
@vercel

vercel Bot commented Nov 16, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
threadlines Ready Ready Preview Nov 16, 2026 10:04am UTC

Request Review

@badcuban
badcuban added this pull request to the merge queue Nov 16, 2026
Merged via the queue into main with commit a7d8b44 Nov 16, 2026
21 checks passed
@badcuban
badcuban deleted the ci/release-smoke-timeout branch November 16, 2026 10:16

This branch was successfully deployed

1 active deployment
Preview — 6b83c575 Deployed Nov 16, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant