Repository navigation
fix(ci): bump Playwright to 1.61.0 (live CDN + Ubuntu 26.04) + job timeout guard - #678
Merged
Merged
Conversation
Playwright <=1.49.1 downloads browsers from playwright.azureedge.net, which Microsoft retired; its postinstall now stalls, hanging `npm ci` until the 6h Actions timeout. This has broken CI on every PR since ~Nov 3 (install step cancelled at 6h), independent of each PR's actual change. 1.50.0 is the smallest release that uses the current CDN (cdn.playwright.dev / playwright.download.prss.microsoft.com). Pin the lockfile to 1.50.0 (smallest viable bump); only playwright-chromium and playwright-core move. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Without a timeout the job inherits the 6h Actions default, so a hung step (like the stalled Playwright CDN download) burns 6 hours before cancelling. Fail fast so breakage is obvious. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
1.50.0 fixed the CDN but is too old for the ubuntu-latest (26.04) runner: "Playwright does not support chromium on ubuntu26.04-x64". Ubuntu 26.04 browser builds were added in 1.61.0, which also uses the current CDN. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
skazinka
marked this pull request as ready for review
November 17, 2026 16:31
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #677
Problem
Every PR's
Lint and testjob had been hanging onnpm cifor ~6 hours (then cancelled at the Actions limit) since ~Nov 3 — repo-wide, independent of each PR's change. Root cause:playwright-chromium/-coreare pinned at 1.44.1, and Playwright ≤ 1.49.1 downloads browsers from the retiredplaywright.azureedge.netCDN, so its postinstall stalls. See #677 for the full diagnosis.Change
apps/slides→playwright-chromium^1.44.1→^1.61.0, lockfile pinned to exactly 1.61.0. Onlyplaywright-chromiumandplaywright-coremove; nothing else in the lockfile drifts.timeout-minutes: 20on theLint and testjob, so any future hung step fails fast instead of burning 6 hours and hiding the cause.Why 1.61.0 (not 1.50.0)
There are two constraints, and the first CI run surfaced the second:
azureedgehost at 1.50.0 (→cdn.playwright.dev/playwright.download.prss.microsoft.com). 1.50.0 fixed the hang —npm cidropped from 6h to ~100s.ubuntu-latest(Ubuntu 26.04) runner and failed fast withPlaywright does not support chromium on ubuntu26.04-x64. Ubuntu 26.04 browser builds were added in 1.61.0 (verified: 1.60.0 has none, 1.61.0 has them).1.61.0 is the smallest version satisfying both — on the current CDN and supporting Ubuntu 26.04.
Verification
Lint and testis green:npm cisucceeds and the fulllint/test/buildpipeline runs in ~2 min (previously: 6h hang).playwright-chromium,playwright-core, both 1.44.1 → 1.61.0).Draft history shows the 1.50.0 → 1.61.0 correction; left unsquashed intentionally.
🤖 Generated with Claude Code