From 96ec7d1a0001e8654caac3efdcefdd6a20e90fad Mon Sep 17 00:00:00 2001 From: github-actions <41898282+github-actions[bot]@users.noreply.github.com> Date: Sat, 21 Sep 2024 10:05:51 +0000 Subject: [PATCH] feat(roll): roll to 1.47 Playwright --- nodejs/versioned_docs/version-stable/ci.mdx | 20 +++++++++---------- .../versioned_docs/version-stable/docker.mdx | 16 +++++++-------- .../version-stable-sidebars.json | 8 ++++---- 3 files changed, 22 insertions(+), 22 deletions(-) diff --git a/nodejs/versioned_docs/version-stable/ci.mdx b/nodejs/versioned_docs/version-stable/ci.mdx index cbbed985ad..0d03d3d2d1 100644 --- a/nodejs/versioned_docs/version-stable/ci.mdx +++ b/nodejs/versioned_docs/version-stable/ci.mdx @@ -101,7 +101,7 @@ jobs: name: 'Playwright Tests' runs-on: ubuntu-latest container: - image: mcr.microsoft.com/playwright:v1.47.1-jammy + image: mcr.microsoft.com/playwright:v1.47.2-jammy steps: - uses: actions/checkout@v4 - uses: actions/setup-node@v4 @@ -341,7 +341,7 @@ trigger: pool: vmImage: ubuntu-latest -container: mcr.microsoft.com/playwright:v1.47.1-noble +container: mcr.microsoft.com/playwright:v1.47.2-noble steps: - task: NodeTool@0 @@ -365,7 +365,7 @@ Running Playwright on CircleCI is very similar to running on GitHub Actions. In executors: pw-jammy-development: docker: - - image: mcr.microsoft.com/playwright:v1.47.1-noble + - image: mcr.microsoft.com/playwright:v1.47.2-noble ``` Note: When using the docker agent definition, you are specifying the resource class of where playwright runs to the 'medium' tier [here](https://circleci.com/docs/configuration-reference?#docker-execution-environment). The default behavior of Playwright is to set the number of workers to the detected core count (2 in the case of the medium tier). Overriding the number of workers to greater than this number will cause unnecessary timeouts and failures. @@ -388,7 +388,7 @@ Jenkins supports Docker agents for pipelines. Use the [Playwright Docker image]( ```groovy pipeline { - agent { docker { image 'mcr.microsoft.com/playwright:v1.47.1-noble' } } + agent { docker { image 'mcr.microsoft.com/playwright:v1.47.2-noble' } } stages { stage('e2e-tests') { steps { @@ -405,7 +405,7 @@ pipeline { Bitbucket Pipelines can use public [Docker images as build environments](https://confluence.atlassian.com/bitbucket/use-docker-images-as-build-environments-792298897.html). To run Playwright tests on Bitbucket, use our public Docker image ([see Dockerfile](./docker.mdx)). ```yml -image: mcr.microsoft.com/playwright:v1.47.1-noble +image: mcr.microsoft.com/playwright:v1.47.2-noble ``` ### GitLab CI @@ -418,7 +418,7 @@ stages: tests: stage: test - image: mcr.microsoft.com/playwright:v1.47.1-noble + image: mcr.microsoft.com/playwright:v1.47.2-noble script: ... ``` @@ -433,7 +433,7 @@ stages: tests: stage: test - image: mcr.microsoft.com/playwright:v1.47.1-noble + image: mcr.microsoft.com/playwright:v1.47.2-noble parallel: 7 script: - npm ci @@ -448,7 +448,7 @@ stages: tests: stage: test - image: mcr.microsoft.com/playwright:v1.47.1-noble + image: mcr.microsoft.com/playwright:v1.47.2-noble parallel: matrix: - PROJECT: ['chromium', 'webkit'] @@ -464,7 +464,7 @@ To run Playwright tests on Google Cloud Build, use our public Docker image ([see ```yml steps: -- name: mcr.microsoft.com/playwright:v1.47.1-noble +- name: mcr.microsoft.com/playwright:v1.47.2-noble script: ... env: @@ -482,7 +482,7 @@ type: docker steps: - name: test - image: mcr.microsoft.com/playwright:v1.47.1-jammy + image: mcr.microsoft.com/playwright:v1.47.2-jammy commands: - npx playwright test ``` diff --git a/nodejs/versioned_docs/version-stable/docker.mdx b/nodejs/versioned_docs/version-stable/docker.mdx index 7a98a63315..7aac496f35 100644 --- a/nodejs/versioned_docs/version-stable/docker.mdx +++ b/nodejs/versioned_docs/version-stable/docker.mdx @@ -21,7 +21,7 @@ This Docker image is intended to be used for testing and development purposes on ### Pull the image ```bash -docker pull mcr.microsoft.com/playwright:v1.47.1-noble +docker pull mcr.microsoft.com/playwright:v1.47.2-noble ``` ### Run the image @@ -33,7 +33,7 @@ By default, the Docker image will use the `root` user to run the browsers. This On trusted websites, you can avoid creating a separate user and use root for it since you trust the code which will run on the browsers. ```bash -docker run -it --rm --ipc=host mcr.microsoft.com/playwright:v1.47.1-noble /bin/bash +docker run -it --rm --ipc=host mcr.microsoft.com/playwright:v1.47.2-noble /bin/bash ``` #### Crawling and scraping @@ -41,7 +41,7 @@ docker run -it --rm --ipc=host mcr.microsoft.com/playwright:v1.47.1-noble /bin/b On untrusted websites, it's recommended to use a separate user for launching the browsers in combination with the seccomp profile. Inside the container or if you are using the Docker image as a base image you have to use `adduser` for it. ```bash -docker run -it --rm --ipc=host --user pwuser --security-opt seccomp=seccomp_profile.json mcr.microsoft.com/playwright:v1.47.1-noble /bin/bash +docker run -it --rm --ipc=host --user pwuser --security-opt seccomp=seccomp_profile.json mcr.microsoft.com/playwright:v1.47.2-noble /bin/bash ``` [`seccomp_profile.json`](https://github.com/microsoft/playwright/blob/main/utils/docker/seccomp_profile.json) is needed to run Chromium with sandbox. This is a [default Docker seccomp profile](https://github.com/docker/engine/blob/d0d99b04cf6e00ed3fc27e81fc3d94e7eda70af3/profiles/seccomp/default.json) with extra user namespace cloning permissions: @@ -74,10 +74,10 @@ See our [Continuous Integration guides](./ci.mdx) for sample configs. See [all available image tags]. We currently publish images with the following tags: -- `:v1.47.1` - Playwright v1.47.1 release docker image based on Ubuntu 24.04 LTS (Noble Numbat). -- `:v1.47.1-noble` - Playwright v1.47.1 release docker image based on Ubuntu 24.04 LTS (Noble Numbat). -- `:v1.47.1-jammy` - Playwright v1.47.1 release docker image based on Ubuntu 22.04 LTS (Jammy Jellyfish). -- `:v1.47.1-focal` - Playwright v1.47.1 release docker image based on Ubuntu 20.04 LTS (Focal Fossa). +- `:v1.47.2` - Playwright v1.47.2 release docker image based on Ubuntu 24.04 LTS (Noble Numbat). +- `:v1.47.2-noble` - Playwright v1.47.2 release docker image based on Ubuntu 24.04 LTS (Noble Numbat). +- `:v1.47.2-jammy` - Playwright v1.47.2 release docker image based on Ubuntu 22.04 LTS (Jammy Jellyfish). +- `:v1.47.2-focal` - Playwright v1.47.2 release docker image based on Ubuntu 20.04 LTS (Focal Fossa). :::note It is recommended to always pin your Docker image to a specific version if possible. If the Playwright version in your Docker image does not match the version in your project/tests, Playwright will be unable to locate browser executables. @@ -101,7 +101,7 @@ To run Playwright inside Docker, you need to have Node.js, [Playwright browsers] ```Dockerfile FROM node:20-bookworm -RUN npx -y playwright@1.47.1 install --with-deps +RUN npx -y playwright@1.47.2 install --with-deps ``` diff --git a/nodejs/versioned_sidebars/version-stable-sidebars.json b/nodejs/versioned_sidebars/version-stable-sidebars.json index 0449d5469b..814f35cb02 100644 --- a/nodejs/versioned_sidebars/version-stable-sidebars.json +++ b/nodejs/versioned_sidebars/version-stable-sidebars.json @@ -511,6 +511,10 @@ "type": "doc", "id": "api/class-fullproject" }, + { + "type": "doc", + "id": "api/class-location" + }, { "type": "doc", "id": "api/class-test" @@ -546,10 +550,6 @@ "type": "category", "label": "Test Reporter", "items": [ - { - "type": "doc", - "id": "api/class-location" - }, { "type": "doc", "id": "api/class-reporter"