diff --git a/.github/workflows/publish.yml b/.github/workflows/publish.yml
index f9cd24ae2..eeb9edc29 100644
--- a/.github/workflows/publish.yml
+++ b/.github/workflows/publish.yml
@@ -53,7 +53,7 @@ jobs:
         working-directory: accessibility-checker/test-act-w3
       - run: gitactions/publish/achecker-engine.sh
         env:
-          NPM_TOKEN: ${{ env.NODE_AUTH_TOKEN }}
+          NPM_TOKEN: ${{ secrets.NODE_AUTH_TOKEN }}
 
   accessibility-checker-publish:
       runs-on: ubuntu-22.04
@@ -82,7 +82,7 @@ jobs:
         working-directory: accessibility-checker
       - run: gitactions/publish/achecker.sh
         env:
-          NPM_TOKEN: ${{ env.NODE_AUTH_TOKEN }}
+          NPM_TOKEN: ${{ secrets.NODE_AUTH_TOKEN }}
 
   karma-accessibility-checker-publish:
       runs-on: ubuntu-22.04
@@ -111,7 +111,7 @@ jobs:
         working-directory: karma-accessibility-checker
       - run: gitactions/publish/karma-achecker.sh
         env:
-          NPM_TOKEN: ${{ env.NODE_AUTH_TOKEN }}
+          NPM_TOKEN: ${{ secrets.NODE_AUTH_TOKEN }}
 
   cypress-accessibility-checker-publish:
       runs-on: ubuntu-22.04
@@ -142,7 +142,7 @@ jobs:
         working-directory: cypress-accessibility-checker
       - run: gitactions/publish/cypress-achecker.sh
         env:
-          NPM_TOKEN: ${{ env.NODE_AUTH_TOKEN }}
+          NPM_TOKEN: ${{ secrets.NODE_AUTH_TOKEN }}
 
   vitest-accessibility-checker-publish:
       runs-on: ubuntu-22.04
@@ -173,7 +173,7 @@ jobs:
         working-directory: vitest-accessibility-checker
       - run: gitactions/publish/vitest-achecker.sh
         env:
-          NPM_TOKEN: ${{ env.NODE_AUTH_TOKEN }}
+          NPM_TOKEN: ${{ secrets.NODE_AUTH_TOKEN }}
 
   extension-build:
     runs-on: ubuntu-22.04
diff --git a/.github/workflows/test.yml b/.github/workflows/test.yml
index a666c692c..d756242f3 100644
--- a/.github/workflows/test.yml
+++ b/.github/workflows/test.yml
@@ -382,10 +382,10 @@ jobs:
       with:
         distribution: 'semeru' # See 'Supported distributions' for available options
         java-version: '17'
-    - name: Chrome 147 (stable with Selenium 4.23.0)
+    - name: Chrome 138 (stable with Selenium 4.34.0)
       uses: browser-actions/setup-chrome@v1
       with:
-        chrome-version: 147
+        chrome-version: 138
         install-chromedriver: true
       id: setup-chrome
     - name: Setup and start rule server
@@ -413,10 +413,10 @@ jobs:
       with:
         distribution: 'semeru' # See 'Supported distributions' for available options
         java-version: '17'
-    - name: Chrome 147 (stable with Selenium 4.23.0)
+    - name: Chrome 138 (stable with Selenium 4.34.0)
       uses: browser-actions/setup-chrome@v1
       with:
-        chrome-version: 147
+        chrome-version: 138
         install-chromedriver: true
       id: setup-chrome
     - name: Setup and start rule server
diff --git a/java-accessibility-checker/pom.xml b/java-accessibility-checker/pom.xml
index 4e243fda9..a4752714a 100644
--- a/java-accessibility-checker/pom.xml
+++ b/java-accessibility-checker/pom.xml
@@ -39,7 +39,7 @@
             <dependency>
                 <groupId>org.junit</groupId>
                 <artifactId>junit-bom</artifactId>
-                <version>5.11.0</version>
+                <version>5.13.0</version>
                 <type>pom</type>
                 <scope>import</scope>
             </dependency>
@@ -75,21 +75,21 @@
         <dependency>
             <groupId>org.mozilla</groupId>
             <artifactId>rhino</artifactId>
-            <version>1.7.14.1</version>
+            <version>1.7.15</version>
         </dependency>
-        <!-- Selenium 4.23.0 has built-in CDP support up to Chrome 127, but works with Chrome up to 147.
-             Chrome 149+ causes CDP errors. Keep chrome-version in .github/workflows/test.yml at 147.
-             When upgrading Selenium, test and update chrome-version accordingly. -->
+        <!-- Selenium 4.34.0 has built-in CDP support up to Chrome 138. Selenium Manager handles
+             chromedriver resolution automatically. Keep chrome-version in .github/workflows/test.yml
+             in sync. When upgrading Selenium, test and update chrome-version accordingly. -->
         <dependency>
             <groupId>org.seleniumhq.selenium</groupId>
             <artifactId>selenium-java</artifactId>
-            <version>4.23.0</version>
+            <version>4.34.0</version>
             <scope>provided</scope>
         </dependency>
         <dependency>
             <groupId>com.microsoft.playwright</groupId>
             <artifactId>playwright</artifactId>
-            <version>1.46.0</version>
+            <version>1.52.0</version>
             <scope>provided</scope>
         </dependency>
     </dependencies>
@@ -108,7 +108,7 @@
             <plugin>
                 <groupId>org.apache.maven.plugins</groupId>
                 <artifactId>maven-source-plugin</artifactId>
-                <version>2.2.1</version>
+                <version>3.3.1</version>
                 <executions>
                     <execution>
                         <id>attach-sources</id>
@@ -121,7 +121,7 @@
             <plugin>
                 <groupId>org.apache.maven.plugins</groupId>
                 <artifactId>maven-gpg-plugin</artifactId>
-                <version>1.5</version>
+                <version>3.2.7</version>
                 <executions>
                   <execution>
                     <id>sign-artifacts</id>
@@ -142,7 +142,7 @@
             <plugin>
                 <groupId>org.apache.maven.plugins</groupId>
                 <artifactId>maven-javadoc-plugin</artifactId>
-                <version>2.9.1</version>
+                <version>3.11.2</version>
                 <executions>
                     <execution>
                         <id>attach-javadocs</id>
@@ -155,7 +155,7 @@
             <plugin>
                 <groupId>org.sonatype.central</groupId>
                 <artifactId>central-publishing-maven-plugin</artifactId>
-                <version>0.5.0</version>
+                <version>0.6.0</version>
                 <extensions>true</extensions>
                 <configuration>
                     <publishingServerId>central</publishingServerId>