@trigger.dev/sdk 4.5.8 → 4.5.9

package/dist/commonjs/version.js

@@ -1,5 +1,5 @@
 "use strict";
 Object.defineProperty(exports, "__esModule", { value: true });
 exports.VERSION = void 0;
-exports.VERSION = "4.5.8";
+exports.VERSION = "4.5.9";
 //# sourceMappingURL=version.js.map

package/dist/esm/version.js

@@ -1,2 +1,2 @@
-export const VERSION = "4.5.8";
+export const VERSION = "4.5.9";
 //# sourceMappingURL=version.js.map

package/docs/ai-chat/changelog.mdx

@@ -1,5 +1,5 @@
 ---
-title: "Changelog"
+title: "AI Agents SDK changelog"
 sidebarTitle: "Changelog"
 description: "Changelog for the AI Agents SDK."
 ---

package/docs/ai-chat/how-it-works.mdx

@@ -1,5 +1,5 @@
 ---
-title: "How it works"
+title: "How the AI Agents SDK works"
 sidebarTitle: "How it works"
 description: "End-to-end mechanics of a chat.agent turn: the two durable channels per session, the long-lived task that reads and writes them, and how a chat survives refreshes, deploys, and idle gaps."
 ---

package/docs/bulk-actions.mdx

@@ -1,5 +1,6 @@
 ---
-title: "Bulk actions"
+title: "Bulk actions in the dashboard"
+sidebarTitle: "Bulk actions"
 description: "Replay or cancel multiple runs from the dashboard using filters or selected run IDs."
 ---
 

package/docs/config/extensions/lightpanda.mdx

@@ -1,5 +1,5 @@
 ---
-title: "Lightpanda"
+title: "Lightpanda build extension"
 sidebarTitle: "lightpanda"
 description: "Use the lightpanda build extension to add Lightpanda browser to your project"
 tag: "v4"

package/docs/config/extensions/puppeteer.mdx

@@ -1,5 +1,5 @@
 ---
-title: "Puppeteer"
+title: "Puppeteer build extension"
 sidebarTitle: "puppeteer"
 description: "Use the puppeteer build extension to enable support for Puppeteer in your project"
 ---

package/docs/how-it-works.mdx

@@ -1,5 +1,5 @@
 ---
-title: "How it works"
+title: "How Trigger.dev works"
 sidebarTitle: "How it works"
 description: "Understand how Trigger.dev works and how it can help you."
 ---
@@ -148,7 +148,7 @@ Here's how the Checkpoint-Resume System works:
 
 2. **Subtask Handling**: If a task needs to trigger a subtask, it can do so and wait for its completion using `triggerAndWait`
 
-3. **State Checkpointing**: While waiting for a subtask or during a programmed pause (e.g., `wait.for({ seconds: 30 })`), the system uses CRIU (Checkpoint/Restore In Userspace) to create a checkpoint of the task's entire state, including memory, CPU registers, and open file descriptors.
+3. **State Checkpointing**: While waiting for a subtask or during a long programmed pause (e.g., `wait.for({ minutes: 5 })`), the system uses CRIU (Checkpoint/Restore In Userspace) to create a checkpoint of the task's entire state, including memory, CPU registers, and open file descriptors. A `wait.for()` or `wait.until()` shorter than 60 seconds doesn't checkpoint — see [Wait](/wait).
 
 4. **Resource Release**: After checkpointing, the parent task's resources are released, freeing up the execution environment.
 
@@ -178,9 +178,9 @@ export const parentTask = task({
     console.log("Child task result:", result);
 
     // This will also cause the task to be checkpointed and suspended
-    await wait.for({ seconds: 30 });
+    await wait.for({ minutes: 5 });
 
-    console.log("Resumed after 30 seconds");
+    console.log("Resumed after 5 minutes");
 
     return "Parent task completed";
   },

package/docs/how-to-reduce-your-spend.mdx

@@ -170,7 +170,7 @@ export const boundedTask = task({
 
 ## Use waitpoints instead of polling
 
-Waits longer than 5 seconds automatically checkpoint your task, meaning you don't pay for compute while waiting. Use `wait.for()`, `wait.until()`, or `triggerAndWait()` instead of polling loops.
+You don't pay for compute during any wait longer than 5 seconds. Use `wait.for()`, `wait.until()`, or `triggerAndWait()` instead of polling loops.
 
 ```ts
 import { task, wait } from "@trigger.dev/sdk";
@@ -178,17 +178,17 @@ import { task, wait } from "@trigger.dev/sdk";
 export const waitpointTask = task({
   id: "waitpoint-task",
   run: async (payload) => {
-    // This wait is free - your task is checkpointed
+    // You aren't charged for compute during this wait
     await wait.for({ minutes: 5 });
 
-    // Parent is also checkpointed while waiting for child tasks
+    // The parent isn't charged either while it waits for a child task
     const result = await childTask.triggerAndWait({ data: payload });
     return result;
   },
 });
 ```
 
-[Read more about waitpoints](/wait-for).
+Waiting saves you compute, but it doesn't always free up concurrency — see [Wait](/wait).
 
 ## Use debounce to consolidate multiple triggers
 

package/docs/queue-concurrency.mdx

@@ -199,6 +199,10 @@ For example, if you have a queue with a `concurrencyLimit` of 1:
 - When the executing run reaches a waitpoint and checkpoints, it releases its slot
 - The next queued run can then begin execution
 
+### Short time-based waits keep their slot
+
+Checkpointing takes time, so a run doesn't checkpoint the moment it reaches a waitpoint. For [`wait.for()`](/wait-for) and [`wait.until()`](/wait-until) it happens 60 seconds into the wait, so anything shorter stays `EXECUTING` and holds its slot for the whole wait. If you're polling in a loop, use an interval comfortably above 60 seconds so the slot is actually released between polls.
+
 ### Waiting for a subtask on a different queue
 
 When a parent task triggers and waits for a subtask on a different queue, the parent task will checkpoint and release its concurrency slot once it reaches the wait point. This prevents environment deadlocks where all concurrency slots would be occupied by waiting tasks.

package/docs/runs/bulk-actions.mdx

@@ -1,5 +1,6 @@
 ---
-title: "Bulk actions"
+title: "Bulk actions with the SDK"
+sidebarTitle: "Bulk actions"
 description: "Cancel or replay many runs from the SDK using run IDs or SDK run-list filters."
 ---
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@trigger.dev/sdk",
-  "version": "4.5.8",
+  "version": "4.5.9",
   "description": "trigger.dev Node.JS SDK",
   "license": "MIT",
   "publishConfig": {
@@ -66,7 +66,7 @@
   "dependencies": {
     "@opentelemetry/api": "1.9.1",
     "@opentelemetry/semantic-conventions": "1.41.1",
-    "@trigger.dev/core": "4.5.8",
+    "@trigger.dev/core": "4.5.9",
     "chalk": "^5.2.0",
     "cronstrue": "^2.21.0",
     "debug": "^4.3.4",