e2e: pin Playwright to 1.59.1
CI / Test (rest) (pull_request) Successful in 34s
CI / Test (store) (pull_request) Successful in 54s
CI / Lint (pull_request) Successful in 26s
CI / Build (windows/amd64) (pull_request) Successful in 26s
CI / Build (linux/amd64) (pull_request) Successful in 25s
CI / Build (linux/arm64) (pull_request) Successful in 25s
e2e / Playwright vs docker-compose (pull_request) Failing after 1m36s
CI / Test (server-http) (pull_request) Successful in 3m19s
CI / Test (rest) (pull_request) Successful in 34s
CI / Test (store) (pull_request) Successful in 54s
CI / Lint (pull_request) Successful in 26s
CI / Build (windows/amd64) (pull_request) Successful in 26s
CI / Build (linux/amd64) (pull_request) Successful in 25s
CI / Build (linux/arm64) (pull_request) Successful in 25s
e2e / Playwright vs docker-compose (pull_request) Failing after 1m36s
CI / Test (server-http) (pull_request) Successful in 3m19s
`@playwright/test` was loose-pinned to ^1.50.0; npm resolved it to 1.59.1 inside the runner image, which only ships browser binaries for 1.50.0. Pin both the package and the docker image to v1.59.1 so deps and binaries stay aligned.
This commit is contained in:
@@ -6,7 +6,7 @@
|
||||
# because the workflow steps execute inside a runner container,
|
||||
# not on the host where compose publishes its ports.
|
||||
|
||||
FROM mcr.microsoft.com/playwright:v1.50.0-jammy
|
||||
FROM mcr.microsoft.com/playwright:v1.59.1-jammy
|
||||
|
||||
WORKDIR /work
|
||||
|
||||
|
||||
Reference in New Issue
Block a user