Skip to content

build: upgrade Playwright to 1.64.0 - #57

Open
dantro86 wants to merge 2 commits into
mainfrom
codex/playwright-upgrade
Open

dantro86 wants to merge 2 commits into
mainfrom
codex/playwright-upgrade

Conversation

@dantro86

@dantro86 dantro86 commented Oct 27, 2026 •

Copy link
Copy Markdown
Collaborator

Summary

  • Upgrade Playwright Java from 1.53.0 to 1.64.0 (Chromium 156.0.8078.4 / revision 1248).
  • Add verified checksums for the new Playwright artifacts and their transitive dependencies;
    dependency verification remains enabled.
  • Keep the existing Chromium installer tied to the same runtime classpath as the tests.

Playwright added Ubuntu 26.04 support in 1.61. This upgrades the outdated browser stack;
it does not replace explicit runner-version pinning.

Scope and merge order

Please merge #55 first to retain explicit Ubuntu 24.04 runner labels. This branch is based on
main and deliberately does not edit workflows, tests, fixtures, or the documentation removed
by #56. An explicit migration to Ubuntu 26.04 remains separate from this upgrade.

Validation

  • Passed locally on macOS arm64: compileTestJava, playwrightInstallChromium, qualityGate
    (160 tests, including concurrent browser-context isolation).
  • Ubuntu 24.04.5 arm64 / Java 21: full qualityGate passed (160 tests) in the official
    Playwright Java 1.64.0 noble container.
  • Fresh SQLite profile on macOS: 108 API and 4 UI cases passed (41 API / 8 UI cases skipped
    by their profile conditions). Local TOTP: all 8 API/UI cases passed.
  • Checked all 17 new verification-metadata artifacts against Maven Central: published SHA-256
    where available; otherwise published SHA-1 matched against the same cached artifact whose
    SHA-256 is recorded in Gradle. No wildcard trust rules or verification bypasses.
  • PR CI at 2926664
    passed completely: configuration contract, framework quality gate, core SQLite API/UI and
    Allure HTML generation. The later commit only relocates the changelog entry to avoid a
    merge conflict with fix(ci): pin Playwright runners to Ubuntu 24.04 #55.
  • Existing configuration matrix, dispatched on this branch:
    TOTP passed on Linux. Direct OIDC and HTTPS/subpath OIDC each pass successful/repeated login
    but fail the two negative cases described below. Other matrix failures are not claimed fixed
    by this dependency upgrade; the full matrix is not green.
  • Local product checks use application image develop@11bb5955a5995570f4b4b03106c847942a311108.

An initial core run hit an incompatible pre-existing SQLite volume (missing monorepo column).
The old volume was preserved and validation was restarted with isolated fresh volumes.

OIDC baseline comparison

In both local OIDC profiles, the unavailable-provider and local-email-conflict scenarios
receive HTTP 500 from Semaphore and time out waiting for /auth/login. Successful login and
repeat login pass. Linux CI exhibits failures in the same two profiles.

The direct OIDC suite was rerun against the same application image with Playwright 1.53.0:
the same two cases failed, while the same two positive cases passed. Thus these failures predate
the upgrade; no assertion, timeout, skip or test fixture is changed to hide them. Proxy OIDC was
not separately rerun with the old dependency. Product/error-handling triage remains a separate task.

References: Java release,
release notes.

@dantro86
dantro86 marked this pull request as ready for review October 27, 2026 09:02

This branch has not been deployed

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant