From ec4865f3c812d49d069b48f72cb8061e027a6623 Mon Sep 17 00:00:00 2001
From: "mintlify[bot]" <109931778+mintlify[bot]@users.noreply.github.com>
Date: Thu, 22 Oct 2026 10:11:02 +0000
Subject: [PATCH] docs: update runtime Node.js versions to the October 2026
 releases

---
 docs/snippets/node-versions.mdx | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/docs/snippets/node-versions.mdx b/docs/snippets/node-versions.mdx
index 2c08cd63f0b..0b57a226163 100644
--- a/docs/snippets/node-versions.mdx
+++ b/docs/snippets/node-versions.mdx
@@ -1,9 +1,9 @@
 Trigger.dev runs your deployed tasks on one of these runtimes:
 
-- Node.js `node` — the default, tracks the current Node.js LTS (today `24.18.0`)
-- Node.js `node-22` — `22.16.0`
-- Node.js `node-24` — `24.18.0`
-- Node.js `node-26` — `26.4.0`
+- Node.js `node` — the default, tracks the current Node.js LTS (today `24.22.1`)
+- Node.js `node-22` — `22.23.4`
+- Node.js `node-24` — `24.22.1`
+- Node.js `node-26` — `26.12.1`
 - Bun `bun` — `1.3.3`
 
 If you don't set a `runtime`, or you set `runtime: "node"`, your tasks run on the current Node.js LTS. That version moves forward as new LTS releases land, so set an explicit version — for example `runtime: "node-24"` — if you need it to stay fixed.