Skip to content

docs: update runtime Node.js versions to the October 2026 releases #5048

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ericallam merged 1 commit into from
Oct 22, 2026
Merged

docs: update runtime Node.js versions to the October 2026 releases #5048

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions docs/snippets/node-versions.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -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.
Expand Down
Loading