fix(cli): allow selecting Bun 1.4 runtime

Add `bun-1.3` and `bun-1.4` as runtime options, mapped to the published
`triggerdotdev/bun:1.3-bookworm` and `1.4-bookworm` images (Bun 1.3.14 and
1.4.2). Bun 1.3.x aborts any fetch that receives no bytes for 300s, which
fails long non-streaming calls; Bun 1.4 does not have that limit.

Plain `bun` is unchanged and still resolves to the 1.3-node20 image. The
versioned images have no node binary, so their final stage starts the app
with `dumb-init bun`. The supervisor pins uid 1001 for every bun runtime.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01XW9yYwuPcYpqPr1zX5pk2W

Author: yulman2207

.changeset/bun-version-runtimes.md

@@ -0,0 +1,16 @@
+---
+"@trigger.dev/core": patch
+"@trigger.dev/rsc": patch
+"trigger.dev": patch
+---
+
+Add `bun-1.3` (Bun 1.3.14) and `bun-1.4` (Bun 1.4.2) as `runtime` options in `trigger.config.ts`. Bun 1.3.x aborts any `fetch` that receives no bytes for 300 seconds, which fails long non-streaming calls such as LLM requests. Bun 1.4 does not have this limit, so set `runtime: "bun-1.4"` for those tasks. `runtime: "bun"` is unchanged and still deploys on Bun 1.3.3.
+
+```ts
+import { defineConfig } from "@trigger.dev/sdk";
+
+export default defineConfig({
+  runtime: "bun-1.4",
+  project: "<your-project-ref>",
+});
+```

apps/supervisor/src/workloadManager/kubernetes.test.ts

@@ -177,7 +177,9 @@ describe("runnerSecurityContext", () => {
   });
 
   it("pins bun's own uid, which differs from node's", () => {
-    expect(runnerSecurityContext("restricted", 1000, "bun")?.runAsUser).toBe(1001);
+    for (const runtime of ["bun", "bun-1.3", "bun-1.4"]) {
+      expect(runnerSecurityContext("restricted", 1000, runtime)?.runAsUser).toBe(1001);
+    }
   });
 
   it("falls back to the configured uid when the runtime is unknown", () => {

apps/supervisor/src/workloadManager/kubernetesPodSpec.ts

@@ -122,7 +122,7 @@ export function runnerSecurityContext(
     allowPrivilegeEscalation: false,
     capabilities: { drop: ["ALL"] },
     ...(level === "restricted"
-      ? { runAsNonRoot: true, runAsUser: runtime === "bun" ? BUN_RUN_AS_USER : runAsUser }
+      ? { runAsNonRoot: true, runAsUser: runtime?.startsWith("bun") ? BUN_RUN_AS_USER : runAsUser }
       : {}),
   };
 }

docs/config/config-file.mdx

@@ -347,6 +347,31 @@ See our [Bun guide](/guides/frameworks/bun) for more information.
 
 <NodeVersions />
 
+### Bun versions
+
+`runtime: "bun"` deploys on Bun `1.3.3`. To pick a Bun release line yourself, use `bun-1.3` (Bun `1.3.14`) or `bun-1.4` (Bun `1.4.2`):
+
+```ts trigger.config.ts
+import { defineConfig } from "@trigger.dev/sdk";
+
+export default defineConfig({
+  project: "<project ref>",
+  // Your other config settings...
+  runtime: "bun-1.4",
+});
+```
+
+<Warning>
+  On Bun 1.3.x (`bun` and `bun-1.3`), `fetch` aborts any request that receives no bytes for 300
+  seconds with `TimeoutError: The operation timed out.`, even if you set a longer `timeout` or
+  `AbortSignal`. A long, non-streaming call, such as an LLM request that returns nothing until it
+  finishes, fails at exactly 5 minutes. Bun 1.4 does not have this limit, so use `bun-1.4` for
+  tasks that make such calls.
+</Warning>
+
+The `bun-1.3` and `bun-1.4` images don't include Node.js, so a task that spawns a `node` process
+needs to stay on `runtime: "bun"`, whose image does.
+
 ## Default machine
 
 You can specify the default machine for all tasks in your project:

docs/guides/frameworks/bun.mdx

@@ -15,14 +15,17 @@ import CliViewRunStep from "/snippets/step-view-run.mdx";
 </Warning>
 
 <Note>
-  **Supported Bun version:** Deployed tasks run on Bun 1.3.3. For local development, use Bun 1.3.x
-  for compatibility.
+  **Supported Bun version:** With `runtime: "bun"`, deployed tasks run on Bun 1.3.3. To deploy on a
+  newer release, set `runtime: "bun-1.4"` (Bun 1.4.2) or `runtime: "bun-1.3"` (Bun 1.3.14), see
+  [Bun versions](/config/config-file#bun-versions). For local development, use the same Bun release
+  line as your deployed runtime.
 </Note>
 
 <Prerequisites framework="Bun" />
 
 ## Known issues
 
+- On Bun 1.3.x (`runtime: "bun"` and `"bun-1.3"`), `fetch` aborts any request that receives no bytes for 300 seconds with `TimeoutError: The operation timed out.`, so a long, non-streaming call such as an LLM request fails at exactly 5 minutes. **Workaround:** set `runtime: "bun-1.4"` in `trigger.config.ts`, which does not have this limit.
 - Certain OpenTelemetry instrumentation will not work with Bun, because Bun does not support Node's `register` hook. This means that some libraries that rely on this hook will not work with Bun.
 - If Bun is installed via Homebrew (e.g. `/opt/homebrew/bin/bun`), you may see an `ENOENT: spawn /Users/<you>/.bun/bin/bun` error because the CLI expects Bun at the default install path. **Workaround:** create a symlink:
   ```bash

docs/self-hosting/overview.mdx

@@ -108,15 +108,15 @@ Deploys build on the published `triggerdotdev/node` and `triggerdotdev/bun` Debi
 DEPLOY_BASE_IMAGES="node-26=registry.example.com/node-fips:26@sha256:<64-character-digest>"
 ```
 
-Entries are comma-separated `runtime=image@sha256:<digest>`. The runtimes are `node-22`, `node-24`, `node-26` and `bun`, and every image must be pinned by digest. An invalid value prevents the webapp from starting. Projects with `runtime: "node"` in their config resolve to the current default Node runtime (`node-24` today), so set that key for them. With the Helm chart, set the variables through `webapp.extraEnvVars`.
+Entries are comma-separated `runtime=image@sha256:<digest>`. The runtimes are `node-22`, `node-24`, `node-26`, `bun`, `bun-1.3` and `bun-1.4`, and every image must be pinned by digest. An invalid value prevents the webapp from starting. Projects with `runtime: "node"` in their config resolve to the current default Node runtime (`node-24` today), so set that key for them. With the Helm chart, set the variables through `webapp.extraEnvVars`.
 
 Runtimes with an entry build on that image; the others keep the published images. Deploys from CLI versions that cannot apply the images are rejected with an error asking to upgrade, and so are `--native-build`, `--local-bundle` and `--from-bundle` deploys. This is a self-hosting setting and does not apply to Trigger.dev Cloud.
 
 You own a custom base image. It must provide:
 
-- `node` on `PATH` at the runtime's major version (for `bun`, both `bun` and `node`, because the final stage starts the app with `dumb-init node`)
+- `node` on `PATH` at the runtime's major version (for `bun`, both `bun` and `node`, because the final stage starts the app with `dumb-init node`; for `bun-1.3` and `bun-1.4`, only `bun`, because the final stage starts the app with `dumb-init bun`)
 - `busybox`, `ca-certificates`, `dumb-init`, `git` and `openssl`
-- a `node` user (a `bun` user for the Bun runtime)
+- a `node` user (a `bun` user for the Bun runtimes)
 - glibc, so native modules built in the build stage load at runtime
 
 A `DEPLOY_BUILD_BASE_IMAGES` image needs everything the base image provides, plus `python3`, `make` and `g++`. Build extensions that add image instructions are replayed on it. Without an entry, the build stage uses the published build image, except for projects whose build extensions add image instructions: those build from your base image and install the toolchain with `apt-get`, so that base must be Debian-based. To avoid the published images entirely, set both variables.

docs/snippets/node-versions.mdx

@@ -5,14 +5,16 @@ Trigger.dev runs your deployed tasks on one of these runtimes:
 - Node.js `node-24` — `24.18.0`
 - Node.js `node-26` — `26.4.0`
 - Bun `bun` — `1.3.3`
+- Bun `bun-1.3` — `1.3.14`
+- Bun `bun-1.4` — `1.4.2`
 
 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.
 
 ```ts
 import { defineConfig } from "@trigger.dev/sdk";
 
 export default defineConfig({
-  // "node", "node-22", "node-24", "node-26" or "bun"
+  // "node", "node-22", "node-24", "node-26", "bun", "bun-1.3" or "bun-1.4"
   runtime: "node-24",
   project: "<your-project-ref>",
 });

packages/cli-v3/src/build/plugins.ts

@@ -1,6 +1,6 @@
 import * as esbuild from "esbuild";
 import { BuildTarget } from "@trigger.dev/core/v3/schemas";
-import { ResolvedConfig } from "@trigger.dev/core/v3/build";
+import { isBunRuntime, ResolvedConfig } from "@trigger.dev/core/v3/build";
 import { configPlugin } from "../config.js";
 import { logger } from "../utilities/logger.js";
 import { bunPlugin } from "../runtimes/bun.js";
@@ -25,7 +25,7 @@ export async function buildPlugins(
 
   plugins.push(polyshedPlugin());
 
-  if (resolvedConfig.runtime === "bun") {
+  if (isBunRuntime(resolvedConfig.runtime)) {
     plugins.push(bunPlugin());
   }
 

packages/cli-v3/src/config.ts

@@ -9,6 +9,7 @@ import type { ResolvedConfig } from "@trigger.dev/core/v3/build";
 import {
   DEFAULT_RUNTIME,
   deprecatedRuntimeReplacement,
+  isBunRuntime,
   isDeprecatedConfigRuntime,
   resolveBuildRuntime,
 } from "@trigger.dev/core/v3/build";
@@ -367,10 +368,10 @@ function validateConfig(config: TriggerConfig, warn = true) {
     );
   }
 
-  if (config.runtime && config.runtime === "bun") {
+  if (isBunRuntime(config.runtime)) {
     warn &&
       prettyWarning(
-        `The "bun" runtime is currently experimental, and certain features may not work, especially opentelemetry instrumentation of 3rd party packages.`
+        `The "${config.runtime}" runtime is currently experimental, and certain features may not work, especially opentelemetry instrumentation of 3rd party packages.`
       );
   }
 }

packages/cli-v3/src/deploy/buildImage.test.ts

@@ -54,6 +54,16 @@ const images: Array<[BuildRuntime, string, string]> = [
     "triggerdotdev/bun:1.3-node20-bookworm@sha256:25b467196277b9d75a37773ee36d28b65ca81a6f41786f7d7d7f1fad95fb5a31",
     "triggerdotdev/bun:1.3-node20-bookworm-build@sha256:a2d5e6d1ec25946ca1d86abdd9ffb9c589376df64ee1b490c461607953931245",
   ],
+  [
+    "bun-1.3",
+    "triggerdotdev/bun:1.3-bookworm@sha256:991ebbc955a793aaebfa619f9cd000d0c9d370a3b8673b705c8364d23a756717",
+    "triggerdotdev/bun:1.3-bookworm-build@sha256:4d90ab4b25ae3bd2f4eda468d94a475b2b73977c5be1497df17b18384cf5ea2d",
+  ],
+  [
+    "bun-1.4",
+    "triggerdotdev/bun:1.4-bookworm@sha256:8d3fdda4309808b9e12e388a4da20dcac72e67449a277b38d7aacc7c50b8e586",
+    "triggerdotdev/bun:1.4-bookworm-build@sha256:ae31fe34246e8b8b9725a8c5366c842ccce59742a0e3a57b42f43f1b251e84a9",
+  ],
 ];
 
 describe("generateContainerfile", () => {
@@ -269,6 +279,27 @@ describe("generateContainerfile", () => {
     }
   });
 
+  it.each([
+    ["bun", "node"],
+    ["bun-1.3", "bun"],
+    ["bun-1.4", "bun"],
+  ] as [BuildRuntime, string][])(
+    "starts the %s app with %s, since only plain bun ships a node binary",
+    async (runtime, binary) => {
+      const containerfile = await generateContainerfile({
+        runtime,
+        build: {},
+        image: undefined,
+        indexScript: "index.js",
+        entrypoint: "entrypoint.js",
+      });
+
+      expect(containerfile).toContain(`ENTRYPOINT [ "dumb-init", "${binary}", "entrypoint.js" ]`);
+      expect(containerfile).toContain('RUN [ "bun", "run", "index.js" ]');
+      expect(containerfile).toContain("USER bun");
+    }
+  );
+
   it("pairs every runtime image with its -build variant", () => {
     for (const runtime of Object.keys(BASE_IMAGE) as BuildRuntime[]) {
       const baseRef = BASE_IMAGE[runtime].split("@")[0];