diff --git a/dotnet/docs/release-notes.mdx b/dotnet/docs/release-notes.mdx
index 5329ac77da2..50444db2dbb 100644
--- a/dotnet/docs/release-notes.mdx
+++ b/dotnet/docs/release-notes.mdx
@@ -11,7 +11,7 @@ import ProgressiveImage from '@theme/ProgressiveImage';
 ## Version 1.55
 
 ### Codegen
-- Automatic `toBeVisible()` assertions: Codegen can now generate automatic `toBeVisible()` assertions for common UI interactions. This feature can be enabled in the Codegen settings UI.
+- Automatic `ToBeVisibleAsync()` assertions: Codegen can now generate automatic `ToBeVisibleAsync()` assertions for common UI interactions. This feature can be enabled in the Codegen settings UI.
 
 ### Breaking Changes
 - ⚠️ Dropped support for Chromium extension manifest v2.
diff --git a/java/docs/ci.mdx b/java/docs/ci.mdx
index d02c986d4eb..c0db41be551 100644
--- a/java/docs/ci.mdx
+++ b/java/docs/ci.mdx
@@ -76,7 +76,7 @@ jobs:
     name: 'Playwright Tests'
     runs-on: ubuntu-latest
     container:
-      image: mcr.microsoft.com/playwright/java:v1.54.0-noble
+      image: mcr.microsoft.com/playwright/java:v1.55.0-noble
       options: --user 1001
     steps:
       - uses: actions/checkout@v4
@@ -161,7 +161,7 @@ trigger:
 
 pool:
   vmImage: ubuntu-latest
-container: mcr.microsoft.com/playwright/java:v1.54.0-noble
+container: mcr.microsoft.com/playwright/java:v1.55.0-noble
 
 steps:
 - task: JavaToolInstaller@0
@@ -184,7 +184,7 @@ Running Playwright on CircleCI is very similar to running on GitHub Actions. In
 executors:
   pw-noble-development:
     docker:
-      - image: mcr.microsoft.com/playwright/java:v1.54.0-noble
+      - image: mcr.microsoft.com/playwright/java:v1.55.0-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.
@@ -195,7 +195,7 @@ Jenkins supports Docker agents for pipelines. Use the [Playwright Docker image](
 
 ```groovy
 pipeline {
-   agent { docker { image 'mcr.microsoft.com/playwright/java:v1.54.0-noble' } }
+   agent { docker { image 'mcr.microsoft.com/playwright/java:v1.55.0-noble' } }
    stages {
       stage('e2e-tests') {
          steps {
@@ -212,7 +212,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/java:v1.54.0-noble
+image: mcr.microsoft.com/playwright/java:v1.55.0-noble
 ```
 
 ### GitLab CI
@@ -225,7 +225,7 @@ stages:
 
 tests:
   stage: test
-  image: mcr.microsoft.com/playwright/java:v1.54.0-noble
+  image: mcr.microsoft.com/playwright/java:v1.55.0-noble
   script:
   ...
 ```
diff --git a/java/docs/docker.mdx b/java/docs/docker.mdx
index 304fa203b40..8d967e529d9 100644
--- a/java/docs/docker.mdx
+++ b/java/docs/docker.mdx
@@ -23,7 +23,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/java:v1.54.0-noble
+docker pull mcr.microsoft.com/playwright/java:v1.55.0-noble
 ```
 
 ### Run the image
@@ -35,7 +35,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/java:v1.54.0-noble /bin/bash
+docker run -it --rm --ipc=host mcr.microsoft.com/playwright/java:v1.55.0-noble /bin/bash
 ```
 
 #### Crawling and scraping
@@ -43,7 +43,7 @@ docker run -it --rm --ipc=host mcr.microsoft.com/playwright/java:v1.54.0-noble /
 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/java:v1.54.0-noble /bin/bash
+docker run -it --rm --ipc=host --user pwuser --security-opt seccomp=seccomp_profile.json mcr.microsoft.com/playwright/java:v1.55.0-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:
@@ -83,7 +83,7 @@ You can run Playwright Server in Docker while keeping your tests running on the
 Start the Playwright Server in Docker:
 
 ```bash
-docker run -p 3000:3000 --rm --init -it --workdir /home/pwuser --user pwuser mcr.microsoft.com/playwright:v1.54.0-noble /bin/sh -c "npx -y playwright@1.54.0 run-server --port 3000 --host 0.0.0.0"
+docker run -p 3000:3000 --rm --init -it --workdir /home/pwuser --user pwuser mcr.microsoft.com/playwright:v1.55.0-noble /bin/sh -c "npx -y playwright@1.55.0 run-server --port 3000 --host 0.0.0.0"
 ```
 
 #### Connecting to the Server
@@ -108,7 +108,7 @@ public class App {
 If you need to access local servers from within the Docker container:
 
 ```bash
-docker run --add-host=hostmachine:host-gateway -p 3000:3000 --rm --init -it --workdir /home/pwuser --user pwuser mcr.microsoft.com/playwright:v1.54.0-noble /bin/sh -c "npx -y playwright@1.54.0 run-server --port 3000 --host 0.0.0.0"
+docker run --add-host=hostmachine:host-gateway -p 3000:3000 --rm --init -it --workdir /home/pwuser --user pwuser mcr.microsoft.com/playwright:v1.55.0-noble /bin/sh -c "npx -y playwright@1.55.0 run-server --port 3000 --host 0.0.0.0"
 ```
 
 This makes `hostmachine` point to the host's localhost. Your tests should use `hostmachine` instead of `localhost` when accessing local servers.
@@ -123,9 +123,9 @@ When running tests remotely, ensure the Playwright version in your tests matches
 See [all available image tags].
 
 We currently publish images with the following tags:
-- `:v1.54.0` - Playwright v1.54.0 release docker image based on Ubuntu 24.04 LTS (Noble Numbat).
-- `:v1.54.0-noble` - Playwright v1.54.0 release docker image based on Ubuntu 24.04 LTS (Noble Numbat).
-- `:v1.54.0-jammy` - Playwright v1.54.0 release docker image based on Ubuntu 22.04 LTS (Jammy Jellyfish).
+- `:v1.55.0` - Playwright v1.55.0 release docker image based on Ubuntu 24.04 LTS (Noble Numbat).
+- `:v1.55.0-noble` - Playwright v1.55.0 release docker image based on Ubuntu 24.04 LTS (Noble Numbat).
+- `:v1.55.0-jammy` - Playwright v1.55.0 release docker image based on Ubuntu 22.04 LTS (Jammy Jellyfish).
 
 :::note
 
diff --git a/java/docs/intro.mdx b/java/docs/intro.mdx
index 21554515c69..fad44a0ac18 100644
--- a/java/docs/intro.mdx
+++ b/java/docs/intro.mdx
@@ -59,7 +59,7 @@ public class App {
     <dependency>
       <groupId>com.microsoft.playwright</groupId>
       <artifactId>playwright</artifactId>
-      <version>1.54.0</version>
+      <version>1.55.0</version>
     </dependency>
   </dependencies>
   <build>
diff --git a/java/docs/release-notes.mdx b/java/docs/release-notes.mdx
index a43e1395ae6..ca25b745554 100644
--- a/java/docs/release-notes.mdx
+++ b/java/docs/release-notes.mdx
@@ -11,7 +11,7 @@ import ProgressiveImage from '@theme/ProgressiveImage';
 ## Version 1.55
 
 ### Codegen
-- Automatic `toBeVisible()` assertions: Codegen can now generate automatic `toBeVisible()` assertions for common UI interactions. This feature can be enabled in the Codegen settings UI.
+- Automatic `isVisible()` assertions: Codegen can now generate automatic `isVisible()` assertions for common UI interactions. This feature can be enabled in the Codegen settings UI.
 
 ### Breaking Changes
 - ⚠️ Dropped support for Chromium extension manifest v2.
diff --git a/java/docs/test-runners.mdx b/java/docs/test-runners.mdx
index 22c0962ccb5..f34ab995e69 100644
--- a/java/docs/test-runners.mdx
+++ b/java/docs/test-runners.mdx
@@ -199,7 +199,7 @@ repositories {
 }
 
 dependencies {
-  implementation 'com.microsoft.playwright:playwright:1.54.0'
+  implementation 'com.microsoft.playwright:playwright:1.55.0'
 }
 
 application {
@@ -232,7 +232,7 @@ repositories {
 }
 
 dependencies {
-  implementation("com.microsoft.playwright:playwright:1.54.0")
+  implementation("com.microsoft.playwright:playwright:1.55.0")
 }
 
 application {
diff --git a/python/docs/release-notes.mdx b/python/docs/release-notes.mdx
index e5e5d735fcf..772a35ba7db 100644
--- a/python/docs/release-notes.mdx
+++ b/python/docs/release-notes.mdx
@@ -11,7 +11,7 @@ import ProgressiveImage from '@theme/ProgressiveImage';
 ## Version 1.55
 
 ### Codegen
-- Automatic `toBeVisible()` assertions: Codegen can now generate automatic `toBeVisible()` assertions for common UI interactions. This feature can be enabled in the Codegen settings UI.
+- Automatic `to_be_visible()` assertions: Codegen can now generate automatic `to_be_visible()` assertions for common UI interactions. This feature can be enabled in the Codegen settings UI.
 
 ### Breaking Changes
 - ⚠️ Dropped support for Chromium extension manifest v2.