Trigger.dev v4.7.1

Better `trigger.dev init` error handling and clearer authorization UX showing which account and organizations you're granting access to.

1 improvement and 1 server change.

Improvements

  • trigger.dev init now stops with a clear error when the target directory has no package.json, instead of installing packages into a parent project. A custom task directory entered during interactive init <path> is now written to trigger.config.ts relative to the project directory.

Server changes

These changes are included in the v4.7.1 Docker image and are already live on Trigger.dev Cloud:

  • The CLI and MCP authorization page now shows the account and organizations you're granting access to.

How to upgrade

Update the trigger.dev/* packages to v4.7.1 using your package manager:


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 users: update your Docker image to ghcr.io/triggerdotdev/trigger.dev:v4.7.1.

Ready to start building?

Build and deploy your first task in 3 minutes.

Get started now