Releases: triggerdotdev/trigger.dev
Releases · triggerdotdev/trigger.dev
@trigger.dev/[email protected]
Patch Changes
- Updated dependencies:
@trigger.dev/[email protected]
@trigger.dev/[email protected]
Major Changes
- Trigger.dev v4 release. Please see our upgrade to v4 docs to view the full changelog: https://trigger.dev/docs/upgrade-to-v4 (#1869)
Patch Changes
- Run Engine 2.0 (alpha) (#1575)
- Updated dependencies:
@trigger.dev/[email protected]
@trigger.dev/[email protected]
Major Changes
- Trigger.dev v4 release. Please see our upgrade to v4 docs to view the full changelog: https://trigger.dev/docs/upgrade-to-v4 (#1869)
Patch Changes
- Now each worker gets it's own pLimit concurrency limiter, and we will only ever dequeue items where there is concurrency capacity, preventing incorrectly retried jobs due to visibility timeout expiry (#2235)
- Updated dependencies:
@trigger.dev/[email protected]
@trigger.dev/[email protected]
Major Changes
- Trigger.dev v4 release. Please see our upgrade to v4 docs to view the full changelog: https://trigger.dev/docs/upgrade-to-v4 (#1869)
Patch Changes
-
Run Engine 2.0 (alpha) (#1575)
-
Added the ability to specify a "createdAt" filter when subscribing to tags in our useRealtime hooks: (#2158)
// Only subscribe to runs created in the last 10 hours useRealtimeRunWithTags("my-tag", { createdAt: "10h" });
You can also now choose to skip subscribing to specific columns by specifying the
skipColumns
option:useRealtimeRun(run.id, { skipColumns: ["usageDurationMs"] });
-
Fixes an issue with realtime when re-subscribing to a run, that would temporarily display stale data and the changes. Now when re-subscribing to a run only the latest changes will be vended (#2162)
-
Updated dependencies:
@trigger.dev/[email protected]
@trigger.dev/[email protected]
Major Changes
- Trigger.dev v4 release. Please see our upgrade to v4 docs to view the full changelog: https://trigger.dev/docs/upgrade-to-v4 (#1869)
Patch Changes
- Updated dependencies:
@trigger.dev/[email protected]
@trigger.dev/[email protected]
@trigger.dev/[email protected]
@trigger.dev/[email protected]
Major Changes
- Trigger.dev v4 release. Please see our upgrade to v4 docs to view the full changelog: https://trigger.dev/docs/upgrade-to-v4 (#1869)
Patch Changes
- The dev command will now use the platform-provided engine URL (#1949)
- Run Engine 2.0 (alpha) (#1575)
- Configurable queue consumer count in supervisor session (#1949)
- Runtime agnostic SDK config via env vars (#2132)
- Add supervisor http client option to disable debug logs (#2116)
- Expose esbuild
keepNames
option (experimental) (#2091) - Add
experimental_autoDetectExternal
trigger config option (#2083) - Add project details to the whoami command (#2231)
- Add import timings and bundle size analysis, the dev command will now warn about slow imports (#2114)
- Improve structured logs (#2062)
-
- Resolve issue where CLI could get stuck during deploy finalization (#2138)
- Unify local and remote build logic, with multi-platform build support
- Improve switch command; now accepts profile name as an argument
- Registry configuration is now fully managed by the webapp
- The deploy
--self-hosted
flag is no longer required - Enhance deployment error reporting and image digest retrieval
-
- Correctly resolve waitpoints that come in early (#2006)
- Ensure correct state before requesting suspension
- Fix race conditions in snapshot processing
- Add optional placement tags to dequeued messages for targeted scheduling (#2390)
- Add verbose structured log level (#2062)
- Suppress external instrumentation for fetch calls from ApiClient (#1788)
- Add runtime version detection for display in the dashboard (#2254)
- Improve metadata flushing efficiency by collapsing operations (#2106)
- fix: Realtime streams: prevent enqueuing into closed ReadableStream (#1781)
- Improve usage flushing (#1931)
- Prevent large outputs from overwriting each other (#1971)
- Fail fast in CI when running deploy with missing
TRIGGER_ACCESS_TOKEN
and add useful error message with link to docs (#2258) - Upgrade to zod 3.25.76 (#2352)
-
- Fix polling interval reset bug that could create duplicate intervals (#1987)
- Protect against unexpected attempt number changes
- Prevent run execution zombies after warm starts
- Managed run controller performance and reliability improvements (#1927)
- v4: New lifecycle hooks (#1817)
- Fix QUEUED status snapshot handler (#1963)
- Fixes an issue with realtime when re-subscribing to a run, that would temporarily display stale data and the changes. Now when re-subscribing to a run only the latest changes will be vended (#2162)
- Expose esbuild
minify
option (experimental) (#2091) - Fix Bun runtime path resolution fallback (#2254)
@trigger.dev/[email protected]
Major Changes
- Trigger.dev v4 release. Please see our upgrade to v4 docs to view the full changelog: https://trigger.dev/docs/upgrade-to-v4 (#1869)
Patch Changes
- Run Engine 2.0 (alpha) (#1575)
- syncVercelEnvVars() fix for syncing the wrong preview branch env vars (#2141)
- Add Lightpanda extension (#2192)
-
- Improve playwright non-headless chrome installation (#2347)
- Prevent spinner message duplication in narrow terminals
- Add ffmpeg v7 support to existing extension:
ffmpeg({ version: "7" })
(#1777) - Add playwright extension (#1764)
- Updated dependencies:
@trigger.dev/[email protected]
[email protected]
Patch Changes
- Make the default of legacyDevProcessCwdBehaviour true instead of false (prevents breaking prismaExtension) (#2387)
- fix: prevent circular reference errors on task indexing when using schemaTask (#2383)
- fix: waitUntil now correctly waits for metadata.streams to finish (#2399)
- fix(runner): prevent retry immediately race condition which can cause stuck runs that end up being system failures (#2402)
- Upgrade to bun v1.2.20 (#2398)
- fix: external traces now respect parent sampling, and prevent broken traces when there is no external trace context (#2395)
- Updated dependencies:
@trigger.dev/[email protected]
@trigger.dev/[email protected]
@trigger.dev/[email protected]
@trigger.dev/[email protected]
Patch Changes
- feat: Support AI SDK 5.0.
ai.tool
now accepts either a schemaTask or a task with a provided jsonSchema (#2396) - Updated dependencies:
@trigger.dev/[email protected]
@trigger.dev/[email protected]
Patch Changes
- Updated dependencies:
@trigger.dev/[email protected]