tag:github.com,2008:https://github.com/triggerdotdev/trigger.dev/releases 2026-03-10T10:17:24Z tag:github.com,2008:Repository/572570113/v4.4.3 2026-03-10T11:13:31Z <h2>Upgrade</h2> <div class="highlight highlight-source-shell notranslate position-relative overflow-auto" data-snippet-clipboard-copy-content="npx trigger.dev@latest update # npm pnpm dlx trigger.dev@latest update # pnpm yarn dlx trigger.dev@latest update # yarn bunx trigger.dev@latest update # bun"><pre>npx trigger.dev@latest update <span class="pl-c"><span class="pl-c">#</span> npm</span> pnpm dlx trigger.dev@latest update <span class="pl-c"><span class="pl-c">#</span> pnpm</span> yarn dlx trigger.dev@latest update <span class="pl-c"><span class="pl-c">#</span> yarn</span> bunx trigger.dev@latest update <span class="pl-c"><span class="pl-c">#</span> bun</span></pre></div> <p>Self-hosted Docker image: <a href="https://github.com/triggerdotdev/trigger.dev/pkgs/container/trigger.dev/727492473?tag=v4.4.3"><code>ghcr.io/triggerdotdev/trigger.dev:v4.4.3</code></a></p> <h2>Release notes</h2> <p>Read the full release notes: <a href="https://trigger.dev/changelog/v4-4-3" rel="nofollow">https://trigger.dev/changelog/v4-4-3</a></p> <h2>What's changed</h2> <h2>Improvements</h2> <ul> <li>Add syncSupabaseEnvVars to pull database connection strings and save them as trigger.dev environment variables (<a href="https://github.com/triggerdotdev/trigger.dev/pull/3152" data-hovercard-type="pull_request" data-hovercard-url="/triggerdotdev/trigger.dev/pull/3152/hovercard">#3152</a>)</li> <li>Auto-cancel in-flight dev runs when the CLI exits, using a detached watchdog process that survives pnpm SIGKILL (<a href="https://github.com/triggerdotdev/trigger.dev/pull/3191" data-hovercard-type="pull_request" data-hovercard-url="/triggerdotdev/trigger.dev/pull/3191/hovercard">#3191</a>)</li> </ul> <h2>Server changes</h2> <p>These changes affect the self-hosted Docker image and Trigger.dev Cloud:</p> <ul> <li> <p>A new Errors page for viewing and tracking errors that cause runs to fail</p> <ul> <li>Errors are grouped using error fingerprinting</li> <li>View top errors for a time period, filter by task, or search the text</li> <li>View occurrences over time</li> <li>View all the runs for an error and bulk replay them (<a href="https://github.com/triggerdotdev/trigger.dev/pull/3172" data-hovercard-type="pull_request" data-hovercard-url="/triggerdotdev/trigger.dev/pull/3172/hovercard">#3172</a>)</li> </ul> </li> <li> <p>Add sidebar tabs (Options, AI, Schema) to the Test page for schemaTask payload generation and schema viewing. (<a href="https://github.com/triggerdotdev/trigger.dev/pull/3188" data-hovercard-type="pull_request" data-hovercard-url="/triggerdotdev/trigger.dev/pull/3188/hovercard">#3188</a>)</p> </li> </ul> <h2>All packages: v4.4.3</h2> <p>@trigger.dev/build, @trigger.dev/core, @trigger.dev/python, @trigger.dev/react-hooks, @trigger.dev/redis-worker, @trigger.dev/rsc, @trigger.dev/schema-to-json, @trigger.dev/sdk, trigger.dev</p> <h2>Contributors</h2> <p>Eric Allam, Matt Aitken, James Ritchie, Oskar Otwinowski</p> <p><strong>Full changelog</strong>: <a class="commit-link" href="https://github.com/triggerdotdev/trigger.dev/compare/v4.4.2...v4.4.3"><tt>v4.4.2...v4.4.3</tt></a></p> github-actions[bot] tag:github.com,2008:Repository/572570113/v.docker.4.4.3 2026-03-10T10:17:24Z <h2>Summary</h2> <p>2 new features, 2 improvements.</p> <h2>Improvements</h2> <ul> <li>Add syncSupabaseEnvVars to pull database connection strings and save<br> them as trigger.dev environment variables<br> (<a href="https://github.com/triggerdotdev/trigger.dev/pull/3152" data-hovercard-type="pull_request" data-hovercard-url="/triggerdotdev/trigger.dev/pull/3152/hovercard">#3152</a>)</li> <li>Auto-cancel in-flight dev runs when the CLI exits, using a detached<br> watchdog process that survives pnpm SIGKILL<br> (<a href="https://github.com/triggerdotdev/trigger.dev/pull/3191" data-hovercard-type="pull_request" data-hovercard-url="/triggerdotdev/trigger.dev/pull/3191/hovercard">#3191</a>)</li> </ul> <h2>Server changes</h2> <p>These changes affect the self-hosted Docker image and Trigger.dev Cloud:</p> <ul> <li> <p>A new Errors page for viewing and tracking errors that cause runs to<br> fail</p> <ul> <li>Errors are grouped using error fingerprinting</li> </ul> </li> <li> <p>View top errors for a time period, filter by task, or search the text</p> <ul> <li>View occurrences over time</li> </ul> </li> <li> <p>View all the runs for an error and bulk replay them<br> (<a href="https://github.com/triggerdotdev/trigger.dev/pull/3172" data-hovercard-type="pull_request" data-hovercard-url="/triggerdotdev/trigger.dev/pull/3172/hovercard">#3172</a>)</p> </li> <li> <p>Add sidebar tabs (Options, AI, Schema) to the Test page for schemaTask<br> payload generation and schema viewing.<br> (<a href="https://github.com/triggerdotdev/trigger.dev/pull/3188" data-hovercard-type="pull_request" data-hovercard-url="/triggerdotdev/trigger.dev/pull/3188/hovercard">#3188</a>)</p> </li> </ul> <details> <summary>Raw changeset output</summary> <h1>Releases</h1> <h2>@trigger.dev/[email protected]</h2> <h3>Patch Changes</h3> <ul> <li>Add syncSupabaseEnvVars to pull database connection strings and save<br> them as trigger.dev environment variables<br> (<a href="https://github.com/triggerdotdev/trigger.dev/pull/3152" data-hovercard-type="pull_request" data-hovercard-url="/triggerdotdev/trigger.dev/pull/3152/hovercard">#3152</a>)</li> <li>Updated dependencies: <ul> <li><code>@trigger.dev/[email protected]</code></li> </ul> </li> </ul> <h2>[email protected]</h2> <h3>Patch Changes</h3> <ul> <li>Auto-cancel in-flight dev runs when the CLI exits, using a detached<br> watchdog process that survives pnpm SIGKILL<br> (<a href="https://github.com/triggerdotdev/trigger.dev/pull/3191" data-hovercard-type="pull_request" data-hovercard-url="/triggerdotdev/trigger.dev/pull/3191/hovercard">#3191</a>)</li> <li>Updated dependencies: <ul> <li><code>@trigger.dev/[email protected]</code></li> <li><code>@trigger.dev/[email protected]</code></li> <li><code>@trigger.dev/[email protected]</code></li> </ul> </li> </ul> <h2>@trigger.dev/[email protected]</h2> <h3>Patch Changes</h3> <ul> <li>Auto-cancel in-flight dev runs when the CLI exits, using a detached<br> watchdog process that survives pnpm SIGKILL<br> (<a href="https://github.com/triggerdotdev/trigger.dev/pull/3191" data-hovercard-type="pull_request" data-hovercard-url="/triggerdotdev/trigger.dev/pull/3191/hovercard">#3191</a>)</li> </ul> <h2>@trigger.dev/[email protected]</h2> <h3>Patch Changes</h3> <ul> <li>Updated dependencies: <ul> <li><code>@trigger.dev/[email protected]</code></li> <li><code>@trigger.dev/[email protected]</code></li> <li><code>@trigger.dev/[email protected]</code></li> </ul> </li> </ul> <h2>@trigger.dev/[email protected]</h2> <h3>Patch Changes</h3> <ul> <li>Updated dependencies: <ul> <li><code>@trigger.dev/[email protected]</code></li> </ul> </li> </ul> <h2>@trigger.dev/[email protected]</h2> <h3>Patch Changes</h3> <ul> <li>Updated dependencies: <ul> <li><code>@trigger.dev/[email protected]</code></li> </ul> </li> </ul> <h2>@trigger.dev/[email protected]</h2> <h3>Patch Changes</h3> <ul> <li>Updated dependencies: <ul> <li><code>@trigger.dev/[email protected]</code></li> </ul> </li> </ul> <h2>@trigger.dev/[email protected]</h2> <h3>Patch Changes</h3> <ul> <li>Updated dependencies: <ul> <li><code>@trigger.dev/[email protected]</code></li> </ul> </li> </ul> <h2>@trigger.dev/[email protected]</h2> <h3>Patch Changes</h3> <ul> <li>Updated dependencies: <ul> <li><code>@trigger.dev/[email protected]</code></li> </ul> </li> </ul> </details> <hr> <p>Co-authored-by: github-actions[bot] &lt;41898282+github-actions[bot]@users.noreply.github.com&gt;<br> Co-authored-by: github-actions[bot] &lt;github-actions[bot]@users.noreply.github.com&gt;</p> github-actions[bot] tag:github.com,2008:Repository/572570113/v4.4.2 2026-03-04T13:38:22Z <h2>Upgrade</h2> <div class="highlight highlight-source-shell notranslate position-relative overflow-auto" data-snippet-clipboard-copy-content="npx trigger.dev@latest update pnpm dlx trigger.dev@latest update yarn dlx trigger.dev@latest update bunx trigger.dev@latest update "><pre>npx trigger.dev@latest update pnpm dlx trigger.dev@latest update yarn dlx trigger.dev@latest update bunx trigger.dev@latest update </pre></div> <p>Self-hosted Docker image: <a href="https://github.com/triggerdotdev/trigger.dev/pkgs/container/trigger.dev/716803036?tag=v4.4.2"><code>ghcr.io/triggerdotdev/trigger.dev:v4.4.2</code></a></p> <h2>Release notes</h2> <p>Read the full release notes: <a href="https://trigger.dev/changelog/v4-4-2" rel="nofollow">https://trigger.dev/changelog/v4-4-2</a></p> <h2>What's changed</h2> <h2>Improvements</h2> <ul> <li>Add input streams for bidirectional communication with running tasks. Define typed input streams with <code>streams.input&lt;T&gt;({ id })</code>, then consume inside tasks via <code>.wait()</code> (suspends the process), <code>.once()</code> (waits for next message), or <code>.on()</code> (subscribes to a continuous stream). Send data from backends with <code>.send(runId, data)</code> or from frontends with the new <code>useInputStreamSend</code> React hook. (<a href="https://github.com/triggerdotdev/trigger.dev/pull/3146" data-hovercard-type="pull_request" data-hovercard-url="/triggerdotdev/trigger.dev/pull/3146/hovercard">#3146</a>)</li> <li>Add PAYLOAD_TOO_LARGE error to handle graceful recovery of sending batch trigger items with payloads that exceed the maximum payload size (<a href="https://github.com/triggerdotdev/trigger.dev/pull/3137" data-hovercard-type="pull_request" data-hovercard-url="/triggerdotdev/trigger.dev/pull/3137/hovercard">#3137</a>)</li> </ul> <h2>Bug fixes</h2> <ul> <li>Fix slow batch queue processing by removing spurious cooloff on concurrency blocks and fixing a race condition where retry attempt counts were not atomically updated during message re-queue. (<a href="https://github.com/triggerdotdev/trigger.dev/pull/3079" data-hovercard-type="pull_request" data-hovercard-url="/triggerdotdev/trigger.dev/pull/3079/hovercard">#3079</a>)</li> <li>fix(sdk): batch triggerAndWait variants now return correct run.taskIdentifier instead of unknown (<a href="https://github.com/triggerdotdev/trigger.dev/pull/3080" data-hovercard-type="pull_request" data-hovercard-url="/triggerdotdev/trigger.dev/pull/3080/hovercard">#3080</a>)</li> </ul> <h2>Server changes</h2> <p>These changes affect the self-hosted Docker image and Trigger.dev Cloud:</p> <ul> <li> <p>Two-level tenant dispatch architecture for batch queue processing. Replaces the<br> single master queue with a two-level index: a dispatch index (tenant → shard)<br> and per-tenant queue indexes (tenant → queues). This enables O(1) tenant<br> selection and fair scheduling across tenants regardless of queue count. Improves batch queue processing performance. (<a href="https://github.com/triggerdotdev/trigger.dev/pull/3133" data-hovercard-type="pull_request" data-hovercard-url="/triggerdotdev/trigger.dev/pull/3133/hovercard">#3133</a>)</p> </li> <li> <p>Add input streams with API routes for sending data to running tasks, SSE reading, and waitpoint creation. Includes Redis cache for fast <code>.send()</code> to <code>.wait()</code> bridging, dashboard span support for input stream operations, and s2-lite support with configurable S2 endpoint, access token skipping, and S2-Basin headers for self-hosted deployments. Adds s2-lite to Docker Compose for local development. (<a href="https://github.com/triggerdotdev/trigger.dev/pull/3146" data-hovercard-type="pull_request" data-hovercard-url="/triggerdotdev/trigger.dev/pull/3146/hovercard">#3146</a>)</p> </li> <li> <p>Speed up batch queue processing by disabling cooloff and increasing the batch queue processing concurrency limits on the cloud:</p> <ul> <li>Pro plan: increase to 50 from 10.</li> <li>Hobby plan: increase to 10 from 5.</li> <li>Free plan: increase to 5 from 1. (<a href="https://github.com/triggerdotdev/trigger.dev/pull/3079" data-hovercard-type="pull_request" data-hovercard-url="/triggerdotdev/trigger.dev/pull/3079/hovercard">#3079</a>)</li> </ul> </li> <li> <p>Move batch queue global rate limiter from FairQueue claim phase to BatchQueue worker queue consumer for accurate per-item rate limiting. Add worker queue depth cap to prevent unbounded growth that could cause visibility timeouts. (<a href="https://github.com/triggerdotdev/trigger.dev/pull/3166" data-hovercard-type="pull_request" data-hovercard-url="/triggerdotdev/trigger.dev/pull/3166/hovercard">#3166</a>)</p> </li> <li> <p>Fix a race condition in the waitpoint system where a run could be blocked by a completed waitpoint but never be resumed because of a PostgreSQL MVCC issue. This was most likely to occur when creating a waitpoint via <code>wait.forToken()</code> at the same moment as completing the token with <code>wait.completeToken()</code>. Other types of waitpoints (timed, child runs) were not affected. (<a href="https://github.com/triggerdotdev/trigger.dev/pull/3075" data-hovercard-type="pull_request" data-hovercard-url="/triggerdotdev/trigger.dev/pull/3075/hovercard">#3075</a>)</p> </li> <li> <p>Fix metrics dashboard chart series colors going out of sync and widgets not reloading stale data when scrolled back into view (<a href="https://github.com/triggerdotdev/trigger.dev/pull/3126" data-hovercard-type="pull_request" data-hovercard-url="/triggerdotdev/trigger.dev/pull/3126/hovercard">#3126</a>)</p> </li> <li> <p>Gracefully handle oversized batch items instead of aborting the stream.</p> <p>When an NDJSON batch item exceeds the maximum size, the parser now emits an error marker instead of throwing, allowing the batch to seal normally. The oversized item becomes a pre-failed run with <code>PAYLOAD_TOO_LARGE</code> error code, while other items in the batch process successfully. This prevents <code>batchTriggerAndWait</code> from seeing connection errors and retrying with exponential backoff.</p> <p>Also fixes the NDJSON parser not consuming the remainder of an oversized line split across multiple chunks, which caused "Invalid JSON" errors on subsequent lines. (<a href="https://github.com/triggerdotdev/trigger.dev/pull/3137" data-hovercard-type="pull_request" data-hovercard-url="/triggerdotdev/trigger.dev/pull/3137/hovercard">#3137</a>)</p> </li> <li> <p>Require the user is an admin during an impersonation session. Previously only the impersonation cookie was checked; now the real user's admin flag is verified on every request. If admin has been revoked, the session falls back to the real user's ID. (<a href="https://github.com/triggerdotdev/trigger.dev/pull/3078" data-hovercard-type="pull_request" data-hovercard-url="/triggerdotdev/trigger.dev/pull/3078/hovercard">#3078</a>)</p> </li> </ul> <h2>All packages: v4.4.2</h2> <p>@trigger.dev/build, @trigger.dev/core, @trigger.dev/python, @trigger.dev/react-hooks, @trigger.dev/redis-worker, @trigger.dev/rsc, @trigger.dev/schema-to-json, @trigger.dev/sdk, trigger.dev</p> <p><strong>Full changelog</strong>: <a class="commit-link" href="https://github.com/triggerdotdev/trigger.dev/compare/v4.4.1...v4.4.2"><tt>v4.4.1...v4.4.2</tt></a></p> github-actions[bot] tag:github.com,2008:Repository/572570113/v.docker.4.4.2 2026-03-04T09:47:24Z <h1>trigger.dev v4.4.2</h1> <h2>Summary</h2> <p>2 new features, 2 improvements, 8 bug fixes.</p> <h2>Improvements</h2> <ul> <li>Add input streams for bidirectional communication with running tasks.<br> Define typed input streams with <code>streams.input&lt;T&gt;({ id })</code>, then consume<br> inside tasks via <code>.wait()</code> (suspends the process), <code>.once()</code> (waits for<br> next message), or <code>.on()</code> (subscribes to a continuous stream). Send data<br> from backends with <code>.send(runId, data)</code> or from frontends with the new<br> <code>useInputStreamSend</code> React hook.<br> (<a href="https://github.com/triggerdotdev/trigger.dev/pull/3146" data-hovercard-type="pull_request" data-hovercard-url="/triggerdotdev/trigger.dev/pull/3146/hovercard">#3146</a>)</li> <li>Add PAYLOAD_TOO_LARGE error to handle graceful recovery of sending<br> batch trigger items with payloads that exceed the maximum payload size<br> (<a href="https://github.com/triggerdotdev/trigger.dev/pull/3137" data-hovercard-type="pull_request" data-hovercard-url="/triggerdotdev/trigger.dev/pull/3137/hovercard">#3137</a>)</li> </ul> <h2>Bug fixes</h2> <ul> <li>Fix slow batch queue processing by removing spurious cooloff on<br> concurrency blocks and fixing a race condition where retry attempt<br> counts were not atomically updated during message re-queue.<br> (<a href="https://github.com/triggerdotdev/trigger.dev/pull/3079" data-hovercard-type="pull_request" data-hovercard-url="/triggerdotdev/trigger.dev/pull/3079/hovercard">#3079</a>)</li> <li>fix(sdk): batch triggerAndWait variants now return correct<br> run.taskIdentifier instead of unknown<br> (<a href="https://github.com/triggerdotdev/trigger.dev/pull/3080" data-hovercard-type="pull_request" data-hovercard-url="/triggerdotdev/trigger.dev/pull/3080/hovercard">#3080</a>)</li> </ul> <h2>Server changes</h2> <p>These changes affect the self-hosted Docker image and Trigger.dev Cloud:</p> <ul> <li> <p>Two-level tenant dispatch architecture for batch queue processing.<br> Replaces the<br> single master queue with a two-level index: a dispatch index (tenant →<br> shard)<br> and per-tenant queue indexes (tenant → queues). This enables O(1) tenant<br> selection and fair scheduling across tenants regardless of queue count.<br> Improves batch queue processing performance.<br> (<a href="https://github.com/triggerdotdev/trigger.dev/pull/3133" data-hovercard-type="pull_request" data-hovercard-url="/triggerdotdev/trigger.dev/pull/3133/hovercard">#3133</a>)</p> </li> <li> <p>Add input streams with API routes for sending data to running tasks,<br> SSE reading, and waitpoint creation. Includes Redis cache for fast<br> <code>.send()</code> to <code>.wait()</code> bridging, dashboard span support for input stream<br> operations, and s2-lite support with configurable S2 endpoint, access<br> token skipping, and S2-Basin headers for self-hosted deployments. Adds<br> s2-lite to Docker Compose for local development.<br> (<a href="https://github.com/triggerdotdev/trigger.dev/pull/3146" data-hovercard-type="pull_request" data-hovercard-url="/triggerdotdev/trigger.dev/pull/3146/hovercard">#3146</a>)</p> </li> <li> <p>Speed up batch queue processing by disabling cooloff and increasing<br> the batch queue processing concurrency limits on the cloud:</p> <ul> <li>Pro plan: increase to 50 from 10.</li> <li>Hobby plan: increase to 10 from 5.</li> </ul> </li> <li> <p>Free plan: increase to 5 from 1.<br> (<a href="https://github.com/triggerdotdev/trigger.dev/pull/3079" data-hovercard-type="pull_request" data-hovercard-url="/triggerdotdev/trigger.dev/pull/3079/hovercard">#3079</a>)</p> </li> <li> <p>Move batch queue global rate limiter from FairQueue claim phase to<br> BatchQueue worker queue consumer for accurate per-item rate limiting.<br> Add worker queue depth cap to prevent unbounded growth that could cause<br> visibility timeouts.<br> (<a href="https://github.com/triggerdotdev/trigger.dev/pull/3166" data-hovercard-type="pull_request" data-hovercard-url="/triggerdotdev/trigger.dev/pull/3166/hovercard">#3166</a>)</p> </li> <li> <p>Fix a race condition in the waitpoint system where a run could be<br> blocked by a completed waitpoint but never be resumed because of a<br> PostgreSQL MVCC issue. This was most likely to occur when creating a<br> waitpoint via <code>wait.forToken()</code> at the same moment as completing the<br> token with <code>wait.completeToken()</code>. Other types of waitpoints (timed,<br> child runs) were not affected.<br> (<a href="https://github.com/triggerdotdev/trigger.dev/pull/3075" data-hovercard-type="pull_request" data-hovercard-url="/triggerdotdev/trigger.dev/pull/3075/hovercard">#3075</a>)</p> </li> <li> <p>Fix metrics dashboard chart series colors going out of sync and<br> widgets not reloading stale data when scrolled back into view<br> (<a href="https://github.com/triggerdotdev/trigger.dev/pull/3126" data-hovercard-type="pull_request" data-hovercard-url="/triggerdotdev/trigger.dev/pull/3126/hovercard">#3126</a>)</p> </li> <li> <p>Gracefully handle oversized batch items instead of aborting the<br> stream.</p> </li> </ul> <p>When an NDJSON batch item exceeds the maximum size, the parser now emits<br> an error marker instead of throwing, allowing the batch to seal<br> normally. The oversized item becomes a pre-failed run with<br> <code>PAYLOAD_TOO_LARGE</code> error code, while other items in the batch process<br> successfully. This prevents <code>batchTriggerAndWait</code> from seeing connection<br> errors and retrying with exponential backoff.</p> <p>Also fixes the NDJSON parser not consuming the remainder of an oversized<br> line split across multiple chunks, which caused "Invalid JSON" errors on<br> subsequent lines.<br> (<a href="https://github.com/triggerdotdev/trigger.dev/pull/3137" data-hovercard-type="pull_request" data-hovercard-url="/triggerdotdev/trigger.dev/pull/3137/hovercard">#3137</a>)</p> <ul> <li>Require the user is an admin during an impersonation session.<br> Previously only the impersonation cookie was checked; now the real<br> user's admin flag is verified on every request. If admin has been<br> revoked, the session falls back to the real user's ID.<br> (<a href="https://github.com/triggerdotdev/trigger.dev/pull/3078" data-hovercard-type="pull_request" data-hovercard-url="/triggerdotdev/trigger.dev/pull/3078/hovercard">#3078</a>)</li> </ul> <details> <summary>Raw changeset output</summary> <h1>Releases</h1> <h2>@trigger.dev/[email protected]</h2> <h3>Patch Changes</h3> <ul> <li>Updated dependencies: <ul> <li><code>@trigger.dev/[email protected]</code></li> </ul> </li> </ul> <h2>[email protected]</h2> <h3>Patch Changes</h3> <ul> <li>Updated dependencies: <ul> <li><code>@trigger.dev/[email protected]</code></li> <li><code>@trigger.dev/[email protected]</code></li> <li><code>@trigger.dev/[email protected]</code></li> </ul> </li> </ul> <h2>@trigger.dev/[email protected]</h2> <h3>Patch Changes</h3> <ul> <li>Updated dependencies: <ul> <li><code>@trigger.dev/[email protected]</code></li> <li><code>@trigger.dev/[email protected]</code></li> <li><code>@trigger.dev/[email protected]</code></li> </ul> </li> </ul> <h2>@trigger.dev/[email protected]</h2> <h3>Patch Changes</h3> <ul> <li>Add input streams for bidirectional communication with running tasks.<br> Define typed input streams with <code>streams.input&lt;T&gt;({ id })</code>, then consume<br> inside tasks via <code>.wait()</code> (suspends the process), <code>.once()</code> (waits for<br> next message), or <code>.on()</code> (subscribes to a continuous stream). Send data<br> from backends with <code>.send(runId, data)</code> or from frontends with the new<br> <code>useInputStreamSend</code> React hook.<br> (<a href="https://github.com/triggerdotdev/trigger.dev/pull/3146" data-hovercard-type="pull_request" data-hovercard-url="/triggerdotdev/trigger.dev/pull/3146/hovercard">#3146</a>)</li> </ul> <p>Upgrade S2 SDK from 0.17 to 0.22 with support for custom endpoints<br> (s2-lite) via the new <code>endpoints</code> configuration, <code>AppendRecord.string()</code><br> API, and <code>maxInflightBytes</code> session option.</p> <ul> <li>Updated dependencies: <ul> <li><code>@trigger.dev/[email protected]</code></li> </ul> </li> </ul> <h2>@trigger.dev/[email protected]</h2> <h3>Patch Changes</h3> <ul> <li>Fix slow batch queue processing by removing spurious cooloff on<br> concurrency blocks and fixing a race condition where retry attempt<br> counts were not atomically updated during message re-queue.<br> (<a href="https://github.com/triggerdotdev/trigger.dev/pull/3079" data-hovercard-type="pull_request" data-hovercard-url="/triggerdotdev/trigger.dev/pull/3079/hovercard">#3079</a>)</li> <li>Updated dependencies: <ul> <li><code>@trigger.dev/[email protected]</code></li> </ul> </li> </ul> <h2>@trigger.dev/[email protected]</h2> <h3>Patch Changes</h3> <ul> <li>Updated dependencies: <ul> <li><code>@trigger.dev/[email protected]</code></li> </ul> </li> </ul> <h2>@trigger.dev/[email protected]</h2> <h3>Patch Changes</h3> <ul> <li>Updated dependencies: <ul> <li><code>@trigger.dev/[email protected]</code></li> </ul> </li> </ul> <h2>@trigger.dev/[email protected]</h2> <h3>Patch Changes</h3> <ul> <li>Add input streams for bidirectional communication with running tasks.<br> Define typed input streams with <code>streams.input&lt;T&gt;({ id })</code>, then consume<br> inside tasks via <code>.wait()</code> (suspends the process), <code>.once()</code> (waits for<br> next message), or <code>.on()</code> (subscribes to a continuous stream). Send data<br> from backends with <code>.send(runId, data)</code> or from frontends with the new<br> <code>useInputStreamSend</code> React hook.<br> (<a href="https://github.com/triggerdotdev/trigger.dev/pull/3146" data-hovercard-type="pull_request" data-hovercard-url="/triggerdotdev/trigger.dev/pull/3146/hovercard">#3146</a>)</li> </ul> <p>Upgrade S2 SDK from 0.17 to 0.22 with support for custom endpoints<br> (s2-lite) via the new <code>endpoints</code> configuration, <code>AppendRecord.string()</code><br> API, and <code>maxInflightBytes</code> session option.</p> <ul> <li> <p>fix(sdk): batch triggerAndWait variants now return correct<br> run.taskIdentifier instead of unknown<br> (<a href="https://github.com/triggerdotdev/trigger.dev/pull/3080" data-hovercard-type="pull_request" data-hovercard-url="/triggerdotdev/trigger.dev/pull/3080/hovercard">#3080</a>)</p> </li> <li> <p>Add PAYLOAD_TOO_LARGE error to handle graceful recovery of sending<br> batch trigger items with payloads that exceed the maximum payload size<br> (<a href="https://github.com/triggerdotdev/trigger.dev/pull/3137" data-hovercard-type="pull_request" data-hovercard-url="/triggerdotdev/trigger.dev/pull/3137/hovercard">#3137</a>)</p> </li> <li> <p>Updated dependencies:</p> <ul> <li><code>@trigger.dev/[email protected]</code></li> </ul> </li> </ul> <h2>@trigger.dev/[email protected]</h2> </details> <hr> <p>Co-authored-by: github-actions[bot] &lt;41898282+github-actions[bot]@users.noreply.github.com&gt;<br> Co-authored-by: github-actions[bot] &lt;github-actions[bot]@users.noreply.github.com&gt;</p> github-actions[bot] tag:github.com,2008:Repository/572570113/build-compute.rc5 2026-03-02T19:35:25Z <p>Merge remote-tracking branch 'origin/main' into feat/compute-workload…</p> nicktrn tag:github.com,2008:Repository/572570113/build-compute.rc4 2026-02-21T11:33:10Z <p>Gates snapshot/restore behaviour independently of compute mode.<br> When disabled, VMs won't receive the metadata URL and suspend/restore<br> are no-ops. Defaults to off so compute mode can be used without snapshots.</p> nicktrn tag:github.com,2008:Repository/572570113/v.docker.4.4.1 2026-02-20T16:40:06Z <p>This PR was opened by the <a href="https://github.com/changesets/action">Changesets<br> release</a> GitHub action. When<br> you're ready to do a release, you can merge this and publish to npm<br> yourself or <a href="https://github.com/changesets/action#with-publishing">setup this action to publish<br> automatically</a>. If<br> you're not ready to do a release yet, that's fine, whenever you add more<br> changesets to main, this PR will be updated.</p> <h1>Releases</h1> <h2>@trigger.dev/[email protected]</h2> <h3>Patch Changes</h3> <ul> <li>Updated dependencies: <ul> <li><code>@trigger.dev/[email protected]</code></li> </ul> </li> </ul> <h2>[email protected]</h2> <h3>Patch Changes</h3> <ul> <li>Add OTEL metrics pipeline for task workers. Workers collect process<br> CPU/memory, Node.js runtime metrics (event loop utilization, event loop<br> delay, heap usage), and user-defined custom metrics via<br> <code>otel.metrics.getMeter()</code>. Metrics are exported to ClickHouse with<br> 10-second aggregation buckets and 1m/5m rollups, and are queryable<br> through the dashboard query engine with typed attribute columns,<br> <code>prettyFormat()</code> for human-readable values, and AI query support.<br> (<a href="https://github.com/triggerdotdev/trigger.dev/pull/3061" data-hovercard-type="pull_request" data-hovercard-url="/triggerdotdev/trigger.dev/pull/3061/hovercard">#3061</a>)</li> <li>Updated dependencies: <ul> <li><code>@trigger.dev/[email protected]</code></li> <li><code>@trigger.dev/[email protected]</code></li> <li><code>@trigger.dev/[email protected]</code></li> </ul> </li> </ul> <h2>@trigger.dev/[email protected]</h2> <h3>Patch Changes</h3> <ul> <li>Updated dependencies: <ul> <li><code>@trigger.dev/[email protected]</code></li> <li><code>@trigger.dev/[email protected]</code></li> <li><code>@trigger.dev/[email protected]</code></li> </ul> </li> </ul> <h2>@trigger.dev/[email protected]</h2> <h3>Patch Changes</h3> <ul> <li>Updated dependencies: <ul> <li><code>@trigger.dev/[email protected]</code></li> </ul> </li> </ul> <h2>@trigger.dev/[email protected]</h2> <h3>Patch Changes</h3> <ul> <li>Updated dependencies: <ul> <li><code>@trigger.dev/[email protected]</code></li> </ul> </li> </ul> <h2>@trigger.dev/[email protected]</h2> <h3>Patch Changes</h3> <ul> <li>Updated dependencies: <ul> <li><code>@trigger.dev/[email protected]</code></li> </ul> </li> </ul> <h2>@trigger.dev/[email protected]</h2> <h3>Patch Changes</h3> <ul> <li>Updated dependencies: <ul> <li><code>@trigger.dev/[email protected]</code></li> </ul> </li> </ul> <h2>@trigger.dev/[email protected]</h2> <h3>Patch Changes</h3> <ul> <li>Add OTEL metrics pipeline for task workers. Workers collect process<br> CPU/memory, Node.js runtime metrics (event loop utilization, event loop<br> delay, heap usage), and user-defined custom metrics via<br> <code>otel.metrics.getMeter()</code>. Metrics are exported to ClickHouse with<br> 10-second aggregation buckets and 1m/5m rollups, and are queryable<br> through the dashboard query engine with typed attribute columns,<br> <code>prettyFormat()</code> for human-readable values, and AI query support.<br> (<a href="https://github.com/triggerdotdev/trigger.dev/pull/3061" data-hovercard-type="pull_request" data-hovercard-url="/triggerdotdev/trigger.dev/pull/3061/hovercard">#3061</a>)</li> <li>Updated dependencies: <ul> <li><code>@trigger.dev/[email protected]</code></li> </ul> </li> </ul> <h2>@trigger.dev/[email protected]</h2> <hr> <p>Co-authored-by: github-actions[bot] &lt;41898282+github-actions[bot]@users.noreply.github.com&gt;<br> Co-authored-by: github-actions[bot] &lt;github-actions[bot]@users.noreply.github.com&gt;</p> github-actions[bot] tag:github.com,2008:Repository/572570113/[email protected] 2026-02-20T16:45:23Z <h3>Patch Changes</h3> <ul> <li>Add OTEL metrics pipeline for task workers. Workers collect process CPU/memory, Node.js runtime metrics (event loop utilization, event loop delay, heap usage), and user-defined custom metrics via <code>otel.metrics.getMeter()</code>. Metrics are exported to ClickHouse with 10-second aggregation buckets and 1m/5m rollups, and are queryable through the dashboard query engine with typed attribute columns, <code>prettyFormat()</code> for human-readable values, and AI query support. (<a href="https://github.com/triggerdotdev/trigger.dev/pull/3061" data-hovercard-type="pull_request" data-hovercard-url="/triggerdotdev/trigger.dev/pull/3061/hovercard">#3061</a>)</li> <li>Updated dependencies: <ul> <li><code>@trigger.dev/[email protected]</code></li> <li><code>@trigger.dev/[email protected]</code></li> <li><code>@trigger.dev/[email protected]</code></li> </ul> </li> </ul> github-actions[bot] tag:github.com,2008:Repository/572570113/@trigger.dev/[email protected] 2026-02-20T16:45:32Z <h3>Patch Changes</h3> <ul> <li>Add OTEL metrics pipeline for task workers. Workers collect process CPU/memory, Node.js runtime metrics (event loop utilization, event loop delay, heap usage), and user-defined custom metrics via <code>otel.metrics.getMeter()</code>. Metrics are exported to ClickHouse with 10-second aggregation buckets and 1m/5m rollups, and are queryable through the dashboard query engine with typed attribute columns, <code>prettyFormat()</code> for human-readable values, and AI query support. (<a href="https://github.com/triggerdotdev/trigger.dev/pull/3061" data-hovercard-type="pull_request" data-hovercard-url="/triggerdotdev/trigger.dev/pull/3061/hovercard">#3061</a>)</li> <li>Updated dependencies: <ul> <li><code>@trigger.dev/[email protected]</code></li> </ul> </li> </ul> github-actions[bot] tag:github.com,2008:Repository/572570113/@trigger.dev/[email protected] 2026-02-20T16:45:20Z <h3>Patch Changes</h3> <ul> <li>Updated dependencies: <ul> <li><code>@trigger.dev/[email protected]</code></li> </ul> </li> </ul> github-actions[bot]