fix: migrate playwright-go to mxschmitt/playwright-go v0.6100.0 (CDN shutdown)

[kdacosta0]

Summary

• Migrate playwright-community/playwright-go → mxschmitt/playwright-go v0.6100.0
• The Playwright /builds/driver CDN (azureedge) has been shut down — playwright install fails with 404
• The module moved to mxschmitt/playwright-go which downloads the driver from npm + nodejs.org instead (PR #615)

Related

• Jira: SECURESIGN-4984

🤖 Generated with Claude Code

[qodo-for-securesign]

PR Summary by Qodo

Fix Playwright install by migrating to mxschmitt/playwright-go v0.6100.0

🐞 Bug fix ⚙️ Configuration changes 🕐 10-20 Minutes

AI Description

• Migrate Playwright Go module to mxschmitt fork to avoid deprecated driver CDN.
• Update setup target to install Playwright drivers via the new module path.
• Bump Go toolchain version and refresh related dependency locks.

Diagram

graph TD
  A["scripts/Makefile (setup)"] --> B(["go run installer"]) --> C(["mxschmitt/playwright-go cmd"]) --> D[["npm registry"]] --> F["Playwright driver"]
  C --> E[["nodejs.org"]] --> F
  G["go.mod/go.sum"] --> C
  H["UI E2E tests"] --> C

  subgraph Legend
    direction LR
    _file["File/config"] ~~~ _svc(["Tool/module"]) ~~~ _ext[["External source"]]
  end

Loading

High-Level Assessment

The following are alternative approaches to this PR:

1. Mirror/override Playwright driver download source

• ➕ Avoids changing the Go module import path/version
• ➕ Can keep using existing fork/version if API stability is critical
• ➖ Requires maintaining a mirror and wiring custom env/config across CI/dev
• ➖ More brittle long-term as upstream download behavior changes

2. Use Node Playwright directly for UI E2E (separate from Go tests)

• ➕ Uses Playwright’s primary ecosystem/tooling
• ➕ Decouples browser tooling lifecycle from Go module dependencies
• ➖ Introduces a second runtime/toolchain and test harness complexity
• ➖ Harder to share fixtures/utilities with existing Go-based tests

3. Vendored/prebuilt Playwright driver binaries in CI images

• ➕ Eliminates network dependency during test runs
• ➕ More reproducible installs
• ➖ Increases image/artifact maintenance burden
• ➖ Needs per-platform handling and periodic updates

Recommendation: Proceed with the current approach: migrating to mxschmitt/playwright-go is the lowest-maintenance fix that aligns with the module’s new supported driver distribution (npm/nodejs.org) after the Azure CDN shutdown. Consider vendoring/prebaking drivers only if CI network instability becomes a recurring issue.

Files changed (4) +10 / -12

Tests (1) +1 / -1

rekor_search_sign_verify_test.goUpdate Playwright import to mxschmitt module path +1/-1

Update Playwright import to mxschmitt module path

• Replaces the playwright-community import with github.com/mxschmitt/playwright-go so UI E2E tests compile against the migrated Playwright Go module.

test/rekorsearchui/rekor_search_sign_verify_test.go

Other (3) +9 / -11

go.modBump Go version and switch Playwright dependency to mxschmitt fork +4/-4

Bump Go version and switch Playwright dependency to mxschmitt fork

• Updates the Go toolchain directive to 1.22 and replaces github.com/playwright-community/playwright-go with github.com/mxschmitt/playwright-go v0.6100.0. Also refreshes a couple of indirect dependency versions as part of the module graph update.

go.mod

go.sumRefresh module checksums for updated Playwright and indirect deps +4/-6

Refresh module checksums for updated Playwright and indirect deps

• Updates go.sum entries to match the new mxschmitt/playwright-go dependency and indirect version bumps, and removes checksums for the old playwright-community module.

go.sum

MakefilePoint Playwright installer to new module path +1/-1

Point Playwright installer to new module path

• Updates the setup target to run the Playwright installer command from github.com/mxschmitt/playwright-go, ensuring driver installation works after the legacy CDN shutdown.

scripts/Makefile

[qodo-for-securesign]

Code Review by Qodo

🐞 Bugs (0) 📘 Rule violations (0) 📎 Requirement gaps (0)

Great, no issues found!

Qodo reviewed your code and found no material issues that require review