v4.7.4

triggerdotdev/trigger.devv4.7.4Oct 14, 2026by github-actions[bot]

Upgrading?

AI Summary

This release focuses on self-hosting enhancements, including custom deploy base images for Docker runtimes, and introduces new MCP tools for AI interaction alongside various dashboard UI, security, and concurrency management improvements.

Key Highlights

  • Custom deploy base images for self-hosted instances via `DEPLOY_BASE_IMAGES` settings
  • New `replay_run` tool in the MCP server for AI-assisted run replaying
  • Concurrency limit overrides via `concurrencyLimits.override()` API
  • Enhanced `runs.replay()` function with options for payload, tags, and delay
  • Security improvements including Cloudflare Turnstile and magic-link browser restrictions

New Features

  • Custom deploy base images for self-hosted instances
  • MCP server `replay_run` tool
  • Concurrency limit override, reset, and retrieve functions
  • Enhanced `runs.replay()` with options
  • Cloudflare Turnstile integration for magic-link sign-in
  • Webhook rate limits based on organization plan
  • Magic-link same-browser requirement
  • Redeploy from deployments list
  • Dashboard live update pausing for idle tabs
  • Log search improvements
  • Parent and root metadata update fixes
  • Webhook delivery improvements for shared IPs

Full Release Notes

# trigger.dev v4.7.4

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

## Release notes

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

## What's changed

## Improvements
- Self-hosted instances can require custom deploy base images per runtime via the new `DEPLOY_BASE_IMAGES` and `DEPLOY_BUILD_BASE_IMAGES` webapp settings. The CLI builds on the images the instance specifies, and older CLIs are rejected with an upgrade message. ([#5005](https://github.com/triggerdotdev/trigger.dev/pull/5005))
- Add a `replay_run` tool to the MCP server, so your AI assistant can replay a run, optionally with a new payload, metadata, tags, machine, version, delay or other trigger options. It is hidden in `--readonly` mode. ([`ff2aa236e`](https://github.com/triggerdotdev/trigger.dev/commit/ff2aa236eb986b938e8e04cec3898b24aed4ec3f))
- Override a concurrency limit's `perKey` for a single `concurrencyKey`: `concurrencyLimits.override(name, { concurrencyKey, perKey, ttl })` caps that one key under that one limit for a while (7 days by default, 30 at most), `reset(name, { concurrencyKey })` clears it, and `retrieve(name, { concurrencyKey })` shows the key's bound and when the override expires. ([`c49fd05f4`](https://github.com/triggerdotdev/trigger.dev/commit/c49fd05f44119ec2a036afaabaad8f9e148a3db6))
- `runs.replay()` now takes options, so you can replay a run with a different payload, metadata, tags, queue, machine, version, delay and other trigger options. Anything you leave out comes from the original run, as before, and the payload is serialized like `trigger()`, so values like `Date` and `BigInt` keep their types. ([`ff2aa236e`](https://github.com/triggerdotdev/trigger.dev/commit/ff2aa236eb986b938e8e04cec3898b24aed4ec3f))
  
  ```ts
  import { runs } from "@trigger.dev/sdk";
  
  await runs.replay("run_1234", {
  payload: { userId: "user_456" },
  tags: ["replayed"],
  delay: "10m",
  });
  ```

## Server changes

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

- Self-hosted instances can add a Cloudflare Turnstile bot check to the magic-link sign-in form by setting `TURNSTILE_SITE_KEY` and `TURNSTILE_SECRET_KEY`. It's off unless both are set.
- Recent deployments started from the GitHub integration or a native CLI deploy can be redeployed from the deployments list, rebuilding the same commit or upload as a new deployment.
- Each webhook endpoint's request rate limit now comes from the organization's plan and can be raised per organization, and the limits page shows it.
- Each environment's webhook endpoints now share a rate limit that counts larger request bodies as more than one request, set by the organization's plan and shown on the limits page.
- Webhooks now appear in the dashboard side menu with a Beta badge, and organizations without access can request beta access from the Webhooks page. The New badges on Sessions, Prompts and Models are gone.
- The new API key dialog's access summary now shows Errors, Webhooks and Waitpoints access, and API keys with waitpoint access can create, list and retrieve waitpoint tokens.
- Log search uses whole-word matching for ASCII alphabetic terms, keeps substring matching for other terms, and incrementally searches older logs without blocking the page.
- Magic links now only sign you in from the browser that requested them, so a link opened elsewhere (including by an email security scanner) no longer logs anyone in. Self-hosted instances can turn this off with `MAGIC_LINK_SAME_BROWSER_REQUIRED=false`.
- The multi-factor authentication login page now focuses the code input, accepts pasted codes, and submits as soon as all six digits are entered.
- Dashboard tabs left in the background now pause their live updates after 30 seconds and catch up as soon as you return, so idle tabs stop reloading data nobody is looking at.
- Preview branch auto-archiving is now always available, with no feature flag to enable first.
- Large run traces now load in chunks and update live without reloading the page, on child run pages as well as root runs.
- The run page shows one clear trace status next to Cancel and Replay: whether the run is live, still loading, only partially shown, or failed to load (with a retry). Search, filters and the run actions now share a single full-width toolbar.
- Keep blank Vercel imports from overwriting existing values when the default-off empty environment variable feature is enabled.
- Errors on the login page, such as an expired or invalid magic link, no longer disappear a moment after the page loads in a new browser.
- Magic-link sign-in emails now always link to `LOGIN_ORIGIN`, whatever host the request came in on.
- Parent and root metadata updates from child tasks no longer stall behind a parent run that is being updated by many children at once, and can optionally be buffered in Redis so they survive a webapp restart.
- Revoking a personal access token is now permanent. Logging in with the CLI again issues a new token instead of reinstating the revoked one, so you can rotate a leaked CLI token by revoking it and running `trigger logout` then `trigger login`.
- Webhook deliveries from a provider's shared IP addresses are no longer throttled by other customers' traffic or by a spoofed `X-Forwarded-For` header; the per-IP limit now applies only to requests for endpoints that don't exist, and every ingest 429 includes `Retry-After`.

## All packages: v4.7.4

@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

Eric Allam, @Mariefay, @d-cs, Oskar Otwinowski, Chris Arderne, @isshaddad, Saadi Myftija, Wes Mason, João Dias, pullfrog[bot], github-actions[bot], @nicktrn, Matt Aitken, @brentshulman-silkline, James Ritchie

**Full changelog**: https://github.com/triggerdotdev/trigger.dev/compare/v4.7.3...v4.7.4

Related Repositories