Skip to content

Commit 94b1fb5

Browse files
docs: update runtime Node.js versions to the October 2026 releases (#5048)
## Summary The runtime list now shows the Node.js versions deploys actually run on: `node-22` 22.23.4, `node-24` (and the default `node`) 24.22.1, and `node-26` 26.12.1. The deploy base images moved to the October 2026 Node.js security releases, so the old patch versions on the page were out of date. Based on [fix(base-images): build node 22, 24 and 26 on the October 2026 Node.js security releases](40f241b34), which bumped the base images. Docs only. Mark ready for review to merge. Co-authored-by: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com>
1 parent b92e46e commit 94b1fb5

1 file changed

Lines changed: 4 additions & 4 deletions

File tree

‎docs/snippets/node-versions.mdx‎

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,9 @@
11
Trigger.dev runs your deployed tasks on one of these runtimes:
22

3-
- Node.js `node` — the default, tracks the current Node.js LTS (today `24.18.0`)
4-
- Node.js `node-22` — `22.16.0`
5-
- Node.js `node-24` — `24.18.0`
6-
- Node.js `node-26` — `26.4.0`
3+
- Node.js `node` — the default, tracks the current Node.js LTS (today `24.22.1`)
4+
- Node.js `node-22` — `22.23.4`
5+
- Node.js `node-24` — `24.22.1`
6+
- Node.js `node-26` — `26.12.1`
77
- Bun `bun` — `1.3.3`
88

99
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.

0 commit comments

Comments
 (0)