v4.5.16
triggerdotdev/trigger.devv4.5.16Sep 2, 2026by github-actions[bot]
AI Summary
This release focuses on improving deployment reliability and performance. It adds warnings for `createRequire` usage, fixes performance issues with large dependency trees, and introduces a durable guard to prevent data loss during database errors in `triggerAndWait` operations.
Key Highlights
- Warnings for `createRequire` usage with suggested fixes to prevent runtime failures.
- Performance improvement for image builds with large dependency trees.
- Durable guard for `triggerAndWait` and `batchTriggerAndWait` to handle database errors.
- Bundler warnings are now displayed in deploy logs.
New Features
- Durable guard for `triggerAndWait` and `batchTriggerAndWait` operations.
- Bundler warnings in deploy output.
Full Release Notes
# trigger.dev v4.5.16 ## Upgrade ```sh 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 ``` Self-hosted Docker image: [`ghcr.io/triggerdotdev/trigger.dev:v4.5.16`](https://github.com/triggerdotdev/trigger.dev/pkgs/container/trigger.dev/1201596204?tag=v4.5.16) ## Release notes Read the full release notes: https://trigger.dev/changelog/v4-5-16 ## What's changed ## Improvements - The `trigger.dev deploy` and `trigger.dev dev` commands now warn (with the suggested fix) when your code loads a package through `createRequire()` that won't be available in the deployed image. Previously it would fail at runtime in production to load the package. Deploys also now show bundler warnings for your code instead of discarding them. ([#4851](https://github.com/triggerdotdev/trigger.dev/pull/4851)) ## Bug fixes - Fixes an issue introduced in 4.5.11 that made deploy image builds of projects with large dependency trees noticeably slower. ([#4878](https://github.com/triggerdotdev/trigger.dev/pull/4878)) ## Server changes These changes affect the self-hosted Docker image and Trigger.dev Cloud: - A durable guard improves reliability for runs waiting on triggerAndWait or batchTriggerAndWait if there's a database error that interrupts a child run finishing. ([#4849](https://github.com/triggerdotdev/trigger.dev/pull/4849)) ## All packages: v4.5.16 @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 ## Contributors Chris Arderne, @d-cs, Matt Aitken, Saadi Myftija, github-actions[bot], James Ritchie **Full changelog**: https://github.com/triggerdotdev/trigger.dev/compare/v4.5.15...v4.5.16