fix: require Node.js 22.23.4, 24.22.1 or 26.12.1 for the eMudhra intermediate CA compromise

.github/workflows/lint.yml

@@ -25,6 +25,8 @@ jobs:
         uses: actions/setup-node@820762786026740c76f36085b0efc47a31fe5020 # v7.0.0
         with:
           node-version-file: '.nvmrc'
+          # the runner cache can hold a 24.x below the engines floor
+          check-latest: true
           cache: 'pnpm'
 
       - name: Install Dependencies

.github/workflows/publish-mcp-registry.yml

@@ -21,6 +21,8 @@ jobs:
         uses: actions/setup-node@820762786026740c76f36085b0efc47a31fe5020 # v7.0.0
         with:
           node-version-file: .nvmrc
+          # the runner cache can hold a 24.x below the engines floor
+          check-latest: true
 
       - name: Install mcp-publisher
         run: |

.github/workflows/release.yml

@@ -45,6 +45,8 @@ jobs:
         with:
           cache: 'pnpm'
           node-version-file: .nvmrc
+          # the runner cache can hold a 24.x below the engines floor
+          check-latest: true
           registry-url: 'https://registry.npmjs.org'
 
       - name: Setup Git

.github/workflows/test.yml

@@ -25,6 +25,8 @@ jobs:
         uses: actions/setup-node@820762786026740c76f36085b0efc47a31fe5020 # v7.0.0
         with:
           node-version-file: '.nvmrc'
+          # the runner cache can hold a 24.x below the engines floor
+          check-latest: true
           cache: 'pnpm'
 
       - name: Install Dependencies

README.md

@@ -941,7 +941,7 @@ Browser mocks require a BiDi-enabled session — start it with `capabilities: {
 
 ### Electron applications
 
-Electron support is local-only and uses the official `@wdio/electron-service` standalone lifecycle. It requires Node.js 22.19 or newer. Put service options such as `appBinaryPath`, `appEntryPoint`, and `appArgs` in `capabilities['wdio:electronServiceOptions']`; use top-level `electronRootDir` for the service's Electron Builder/Electron Forge discovery. When testing a binary outside the project, set `browserVersion` to the Electron version so the service can select a compatible Chromedriver.
+Electron support is local-only and uses the official `@wdio/electron-service` standalone lifecycle. It requires Node.js 22.23.4, 24.22.1, 26.12.1 or a later release of these lines, as the server does. Put service options such as `appBinaryPath`, `appEntryPoint`, and `appArgs` in `capabilities['wdio:electronServiceOptions']`; use top-level `electronRootDir` for the service's Electron Builder/Electron Forge discovery. When testing a binary outside the project, set `browserVersion` to the Electron version so the service can select a compatible Chromedriver.
 
 ```javascript
 start_session({

package.json

@@ -32,7 +32,7 @@
   },
   "license": "MIT",
   "engines": {
-    "node": ">=22.19.0"
+    "node": ">=22.23.4 <23 || >=24.22.1 <25 || >=26.12.1"
   },
   "publishConfig": {
     "access": "public"

tests/utils/docs-index.test.ts

@@ -563,7 +563,8 @@ const EXPECTATIONS: Expectation[] = [
   { query: 'newWindow', title: 'newWindow', maxRank: 1 },
   { query: 'appium setup', path: '/docs/appium.md', maxRank: 1 },
   { query: 'appium service configuration', path: '/docs/appium-service.md', maxRank: 1 },
-  { query: 'appium capabilities', path: '/docs/api/appium.md', maxRank: 1 },
+  // The live Capabilities page outranks it since 2026-10-21; both pages answer the query.
+  { query: 'appium capabilities', path: '/docs/api/appium.md', maxRank: 2 },
   { query: 'appium capabilities', path: '/docs/capabilities.md', maxRank: 3 },
   { query: 'custom reporter', path: '/docs/customreporter.md', maxRank: 1 },
   { query: 'mcp transport', path: '/docs/mcp/transport.md', maxRank: 1 },