Skip to content

trigger.dev v4.6.1

Choose a tag to compare

View all tags
@github-actions github-actions released this 15 Sep 15:55
· 28 commits to main since this release
v4.6.1
4132259
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

trigger.dev v4.6.1

Upgrade

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.6.1

Release notes

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

What's changed

Improvements

  • Show schedule policy warnings during development and deployment, and present Free plan schedule limits without internal stack traces. (723fde4a8)
  • New CLI commands: projects create/get/rename, runs list/get/replay/cancel, and env set (5bcd1a9fa)
  • Warn when a deployment uses the deprecated Node.js 21 runtime. Deployment logs now include upgrade guidance, and the account associated with the deployment receives an email notification. (053b0b4c6)

Bug fixes

  • Fix the MCP server failing every tools/list call with "Date cannot be represented in JSON Schema" (6c90639f2)

Server changes

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

  • The assistant in the dashboard now answers with cards: investigation cards for run questions, carrying the run's timeline and links to the run, queue or deployment, alongside charts and tables you can open fullscreen or copy — including queue metrics — and it answers about another project or environment without you switching to it first. The assistant reads run timelines through a dedicated endpoint, so span durations and launch events are consistent on every event store; the public run trace API is unchanged.
  • Warn when Production projects still use Node.js 21 and link directly to update instructions
  • Deployments now show the runtime their worker actually reported, so Bun deployments are no longer labelled Node.js; a deployment with no recorded runtime shows a dash instead of a guess.

All packages: v4.6.1

@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, claude[bot], github-actions[bot], @isshaddad, Eric Allam, Katia Bulatova

Full changelog: v4.6.0...v4.6.1

Contributors

isshaddad
Assets 2
Loading