Skip to content

Required e2e check now fails on every PR: ubuntu-latest runner moved to 26.04, unsupported by pinned Playwright 1.60.0 #671

Open

Description

@rosscado

Problem: The required e2e status check (.github/workflows/e2e.yaml) fails on every PR, regardless of diff content, because GitHub Actions' ubuntu-latest label now resolves to Ubuntu 26.04, and the repo's pinned @playwright/test@^1.60.0 cannot install Chromium's OS dependencies on that image.

Scope: Blocks the required e2e check for every PR in the repo (it is diff-independent — the failure happens before any test file runs). Confirmed on PR #670 (a docs-only change: one new file under doc/audit-reports/, nothing touching CI config, Playwright, or the extension). test (22.x) is unaffected (no Playwright browser install). e2e-firefox is unaffected (it drives Firefox via geckodriver/Marionette, not a Playwright-installed browser) — confirmed green on the same PR run. This is purely the Chromium-based e2e job (runs-on: ubuntu-latest in .github/workflows/e2e.yaml; test.yaml also runs on ubuntu-latest but never installs a Playwright browser, so it's unaffected by this specific incompatibility).

Reproduction:

  1. Open any PR against main (verified on PR docs(audit): 2026-11-02 constitution-vs-reality audit — zero new drift #670, run https://github.com/Pedal-Intelligence/saypi-userscript/actions/runs/41401514311).
  2. The e2e job's "Install Playwright Chromium + OS deps" step runs npx playwright install --with-deps chromium.
  3. It fails immediately (~1s) with:
    BEWARE: your OS is not officially supported by Playwright; installing dependencies for ubuntu26.04-x64 as a fallback.
    Cannot install dependencies for ubuntu26.04-x64 with Playwright 1.60.0!
    Failed to install browsers
    Error: ERROR: Playwright does not support chromium on ubuntu26.04-x64
    ##[error]Process completed with exit code 1.
    
  4. Every prior run back through 2026-09-06 (10+ runs) was green on the same workflow, using the same pinned Playwright version — this is a regression caused by GitHub's hosted-runner image rollout, not a code change in this repo. The last known-green e2e run was on main@e7498a3 (2026-10-12); this is the first PR/push to trigger the workflow since then, so the rollout landed sometime in the intervening ~3 weeks.

Acceptance criteria:

  • The e2e required check passes again on a fresh PR with no unrelated changes.
  • Either (a) .github/workflows/e2e.yaml's e2e job is pinned to a runner image Playwright 1.60.0 supports (e.g. ubuntu-24.04) as an immediate stopgap, or (b) @playwright/test (and its browser binaries, and the pinned Chromium revision referenced in e2e/README.md/sandbox tooling if applicable) is upgraded to a version that supports installing Chromium on Ubuntu 26.04 — whichever the founder prefers.
  • Whichever fix lands, re-verify green on a real PR run (not just a local claim), since the failure is runner-image-specific and only observable in CI.

Notes/Hypotheses (non-binding): The fix touches .github/workflows/e2e.yaml, which scripts/path-guard-lib.mjs's GATED_PATH_PATTERNS treats as a founder-gated path (per AGENTS.md's high-blast-radius list: "MV2/MV3 manifest, permissions, or content-script injection scope" doesn't literally cover this, but .github/workflows/ itself is explicitly gated) — so an autonomous agent cannot push the fix without the PR carrying the founder-approved label. Flagging this as awaiting-founder for that reason, not because the diagnosis is uncertain.

Surfaced by the 2026-11-02 constitution-vs-reality audit (doc/constitution-audit.md, #535) via its own audit PR's CI run — see doc/audit-reports/2026-11-02.md.

Activity

  1. added
    bugSomething isn't working
    awaiting-founderBlocked on a founder decision or sign-off — needs Ross's attention
    on Nov 2, 2026
  2. github-actions commented on Nov 2, 2026

    @github-actions

    @rosscado — this is now awaiting a founder decision or sign-off (awaiting-founder applied by @rosscado). See the latest comment/description for what's being asked. Standing queue: open items with this label.

  3. rosscado commented on Nov 2, 2026

    @rosscado
    ContributorAuthor

    awaiting-founder: this blocks the required e2e check on every PR in the repo (verified diff-independent — reproduces on a docs-only PR). The fix requires editing .github/workflows/e2e.yaml, a founder-gated path per path-guard/AGENTS.md's high-blast-radius list, so no agent can push it without a founder-approved label on the fix PR.

    What's being asked: a decision on which stopgap/fix to take — (a) pin the e2e job's runs-on to ubuntu-24.04 (fast, reversible, keeps the pinned Playwright version), or (b) upgrade @playwright/test to a version that supports Ubuntu 26.04 (larger diff, revisits the pinned Chromium revision other tooling/docs reference) — and sign-off (founder-approved label) on whichever PR implements it, since until then no autonomous session can land a fix to this file.


    Generated by Claude Code

  4. rosscado commented on Nov 16, 2026

    @rosscado
    ContributorAuthor

    Weekly maintenance routine (2026-11-16): one additional data point for the decision, no action taken.

    Still awaiting-founder, still blocking the required e2e check on every PR — confirmed unchanged since 2026-11-02.

    npm outdated (fresh npm ci this run) shows @playwright/test at installed 1.60.0, with 1.65.1 as both "Wanted" (i.e. already permitted by package.json's existing ^1.60.0 range) and "Latest". That means option (b) — upgrading @playwright/test — may not require a package.json range edit at all, just a lockfile refresh (npm install) to pick up 1.65.1 within the already-declared range. Not verified here whether 1.65.1's bundled browser-install step actually supports Ubuntu 26.04 (this cloud routine doesn't run the e2e job or touch .github/workflows/), so this doesn't resolve whether (b) works — only that it's cheaper to try than a true major bump would be, if the founder leans toward (b) over pinning runs-on: ubuntu-24.04.

    No changes made; .github/workflows/e2e.yaml stays founder-gated.


    Generated by Claude Code

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

    awaiting-founderBlocked on a founder decision or sign-off — needs Ross's attentionbugSomething isn't working

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions