fix(ci): pin selftest Playwright image to v1.61.1 matching lockfile
CI / release (pull_request) Has been skipped
CI / skip-ci-check (pull_request) Successful in 5s
CI / secret-scan (pull_request) Successful in 5s
CI / build-and-test (pull_request) Successful in 18s
CI / selftest (pull_request) Successful in 39s

npm ci was resolving @playwright/test@1.61.1 against a v1.52.0 container,
so Chromium binary paths mismatched and browser specs failed.
This commit is contained in:
2026-07-15 09:00:31 -04:00
parent afaa987218
commit 68b04bd826
3 changed files with 7 additions and 5 deletions
+5 -3
View File
@@ -37,6 +37,8 @@ public e2e must keep the default forbid-private behavior.
## CI
`.gitea/workflows/ci.yml` job `selftest` installs Chromium deps and runs
`npm run selftest` after unit tests. Failures there mean a regression in kit
browser/API helpers *before* a consumer pins a broken tag.
`.gitea/workflows/ci.yml` job `selftest` runs in
`mcr.microsoft.com/playwright:v1.61.1-jammy` (must match the pinned
`@playwright/test` version) and executes `npm run selftest` after unit tests.
Failures there mean a regression in kit browser/API helpers *before* a consumer
pins a broken tag.