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

[kdacosta0]

Summary

• Migrate playwright-community/playwright-go → mxschmitt/playwright-go (one-line change)
• 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 PRs

• sigstore-e2e: fix: migrate playwright-go to mxschmitt/playwright-go v0.6100.0 sigstore-e2e#80
• releases: https://github.com/securesign/releases/pull/291
• pipelines: fix: migrate playwright-go to mxschmitt/playwright-go (CDN shutdown) pipelines#548
• Jira: SECURESIGN-4984

🤖 Generated with Claude Code

[qodo-for-securesign]

Code Review by Qodo

Sorry, something went wrong

We weren't able to complete the code review on our side. Please try again

[qodo-for-securesign]

PR Summary by Qodo

Fix CI Playwright install by switching to mxschmitt/playwright-go (CDN shutdown)

🐞 Bug fix ⚙️ Configuration changes 🕐 Less than 5 minutes

AI Description

• Switch CI Playwright installer module to avoid azureedge CDN 404 failures.
• Keep the same install command/flags while changing the Go module path.
• Restore E2E UI test setup reliability in GitHub Actions.

Diagram

graph TD
  A["GitHub Actions"] --> B["E2E job"] --> C["Playwright install step"] --> D["go run mxschmitt/playwright-go"] --> E["Browser/driver download"]

  subgraph Legend
    direction LR
    _ci["CI runner"] ~~~ _step["Workflow step"] ~~~ _ext["External download"]
  end

Loading

High-Level Assessment

The following are alternative approaches to this PR:

1. Install Playwright via npm instead of Go module CLI

• ➕ Aligns with Playwright’s primary distribution channel
• ➕ Potentially clearer caching/versioning via package-lock
• ➖ Adds Node/npm toolchain management to the workflow
• ➖ May diverge from existing Go-based test harness expectations

2. Pin and cache Playwright browsers/drivers in CI

• ➕ Reduces reliance on external download availability during runs
• ➕ Speeds up CI by avoiding repeated downloads
• ➖ More workflow complexity (cache keys, invalidation, storage)
• ➖ Does not by itself fix a broken upstream download host

3. Override download host via env/config (if supported upstream)

• ➕ Minimal code/module churn
• ➕ Can be toggled quickly if endpoints change again
• ➖ Depends on upstream supporting a stable override mechanism
• ➖ Still ties reliability to another external host

Recommendation: Proceed with the current approach: switching to mxschmitt/playwright-go is the smallest, most targeted fix to restore playwright install after the azureedge CDN shutdown, with minimal workflow change surface. Consider adding caching later if CI runtime becomes a concern.

Files changed (1) +1 / -1

Other (1) +1 / -1

main.ymlUse mxschmitt/playwright-go for Playwright installation in CI +1/-1

Use mxschmitt/playwright-go for Playwright installation in CI

• Updates the E2E job’s Playwright install command to run the CLI from 'github.com/mxschmitt/playwright-go' instead of 'playwright-community/playwright-go'. This avoids failures caused by the shutdown of the previous driver CDN endpoint while keeping the install flags unchanged.

.github/workflows/main.yml