v4.5.5

Dokploy/dokployv4.5.5Jul 20, 2026by github-actions[bot]

AI Summary

A performance and stability update adding support for newer Node.js versions, optimizing database read traffic, and fixing several dashboard and API issues.

Key Highlights

  • Experimental Node.js 24 and 26 task runtimes added
  • ClickHouse read replica support for performance optimization
  • Fix for batchTrigger idempotency key failures
  • Dashboard now reloads automatically during deployment

New Features

  • Experimental Node.js 24 and 26 task runtimes
  • defaultRegion field added to project GET and list API responses
  • Optional ClickHouse read replica routing for read traffic
  • Request rate limiting for telemetry ingestion endpoints
  • Fix for batchTrigger requests failing when using idempotency keys
  • Speed up idempotency checks on large batchTrigger calls
  • Dashboard auto-reload to recover from unstyled pages during deploy

Full Release Notes

# trigger.dev v4.5.5

## 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.5`](https://github.com/triggerdotdev/trigger.dev/pkgs/container/trigger.dev/1048241799?tag=v4.5.5)

## Release notes

Read the full release notes: https://trigger.dev/changelog/v4-5-5

## What's changed

## Improvements
- Add experimental Node.js 24 and 26 task runtimes. Set `runtime` to `experimental-node-24` or `experimental-node-26` in `trigger.config.ts`. ([#4085](https://github.com/triggerdotdev/trigger.dev/pull/4085))
- Add `defaultRegion` to the project GET and list API responses; null when unset. ([#4146](https://github.com/triggerdotdev/trigger.dev/pull/4146))

## Server changes

These changes affect the self-hosted Docker image and Trigger.dev Cloud:

- Transient internal sync failures are now retried quietly instead of surfacing as errors. ([#4270](https://github.com/triggerdotdev/trigger.dev/pull/4270))
- Optionally route ClickHouse read traffic to a read replica while writes stay on the primary. Set `CLICKHOUSE_READER_URL` to move all reads, or target the busiest paths with `RUNS_LIST_CLICKHOUSE_URL` (runs list) and `EVENTS_READER_CLICKHOUSE_URL` (traces, spans, logs). All optional; unset keeps current behavior. ([#4081](https://github.com/triggerdotdev/trigger.dev/pull/4081))
- Remove the deprecated realtime stream write endpoint used by retired v3 task clients. ([#4250](https://github.com/triggerdotdev/trigger.dev/pull/4250))
- Fix batchTrigger requests that set a per-item idempotency key failing with an error instead of creating and deduplicating the runs ([#4271](https://github.com/triggerdotdev/trigger.dev/pull/4271))
- Speed up idempotency checks on `batchTrigger` calls that use idempotency keys. Large batches against a task with a big run history no longer degrade to multi-second lookups. ([#4255](https://github.com/triggerdotdev/trigger.dev/pull/4255))
- The "Preview branches" usage on the Limits page now counts only preview branches. ([#4283](https://github.com/triggerdotdev/trigger.dev/pull/4283))
- Avoid opening a redundant database connection pool when the legacy and primary databases are the same server, preventing connection usage from doubling. ([#4253](https://github.com/triggerdotdev/trigger.dev/pull/4253))
- Fix pages occasionally loading unstyled or failing to load during a deploy. The dashboard now reloads automatically to recover. ([#4282](https://github.com/triggerdotdev/trigger.dev/pull/4282))

## All packages: v4.5.5

@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, @nicktrn, @d-cs, Eric Allam, github-actions[bot], @isshaddad, Katia Bulatova, Matt Aitken

**Full changelog**: https://github.com/triggerdotdev/trigger.dev/compare/v4.5.4...v4.5.5