GeezerVison

Sourced from trigger.dev's releases.

[email protected]

Patch Changes

• Add OTEL metrics pipeline for task workers. Workers collect process CPU/memory, Node.js runtime metrics (event loop utilization, event loop delay, heap usage), and user-defined custom metrics via otel.metrics.getMeter(). Metrics are exported to ClickHouse with 10-second aggregation buckets and 1m/5m rollups, and are queryable through the dashboard query engine with typed attribute columns, prettyFormat() for human-readable values, and AI query support. (#3061)
• Updated dependencies:
  • @trigger.dev/[email protected]
  • @trigger.dev/[email protected]
  • @trigger.dev/[email protected]

[email protected]

Patch Changes

• Fix runner getting stuck indefinitely when execute() is called on a dead child process. (#2978)
• Add optional timeoutInSeconds parameter to the wait_for_run_to_complete MCP tool. Defaults to 60 seconds. If the run doesn't complete within the timeout, the current state of the run is returned instead of waiting indefinitely. (#3035)
• Fixed a minor issue in the deployment command on distinguishing between local builds for the cloud vs local builds for self-hosting setups. (#3070)
• Updated dependencies:
  • @trigger.dev/[email protected]
  • @trigger.dev/[email protected]
  • @trigger.dev/[email protected]

[email protected]

Patch Changes

• Updated dependencies:
  • @trigger.dev/[email protected]
  • @trigger.dev/[email protected]
  • @trigger.dev/[email protected]

[email protected]

Patch Changes

• fix(cli): update command should preserve existing package.json order (#2810)
• Updated dependencies:
  • @trigger.dev/[email protected]
  • @trigger.dev/[email protected]
  • @trigger.dev/[email protected]

Sourced from trigger.dev's changelog.

4.5.9

Patch Changes

• trigger mcp now always starts the MCP server, and the interactive install wizard has moved behind trigger mcp --install. Previously the wizard opened whenever stdout was a terminal, so any MCP host that spawns the command over a pseudo-terminal waited on a server that never started and eventually timed out. (#4131)

• Ask whether an environment is healthy and get an answer instead of a wall of charts. trigger report health returns a verdict on three questions: is work flowing, are the runs that start succeeding, and is the telemetry fresh enough to trust either answer. When something looks wrong it names the most likely cause and a next action. (#4131)

  npx trigger.dev@latest report health --env prod --period 24h

  The verdict is computed server side, so the CLI, the new get_report MCP tool, and GET /api/v1/reports/health all return the same text with the same sparklines. In MCP hosts that support prompts, report is also available as a slash command.

• Prevent build debug logs from including environment variable values. (#4420)

• Send the running CLI version when checking for platform notifications so notices can be limited to compatible CLI releases. (#4407)

• Updated dependencies:

  • @trigger.dev/[email protected]
  • @trigger.dev/[email protected]
  • @trigger.dev/[email protected]

4.5.8

Patch Changes

• Updated dependencies:
  • @trigger.dev/[email protected]
  • @trigger.dev/[email protected]
  • @trigger.dev/[email protected]

4.5.7

Patch Changes

• Fixes intermittent trigger dev run crashes where a run could fail at boot with a cryptic Cannot find module .../dev-run-worker.mjs after a rebuild had cleaned up the build directory the run was launched against. Dev runs now retry cleanly instead of hard-crashing when their build directory is missing, the dev watchdog no longer removes the build tree of a still-running session, and a run assigned to a worker version that was superseded by a rebuild now fails fast with a clear message instead of silently hanging until it times out. (#4276)

• Add node-24 and node-26 as supported runtime options in trigger.config.ts. The experimental-node-24 and experimental-node-26 names are now deprecated aliases and emit a deprecation warning; switch to node-24 / node-26 instead. (#4337)

  import { defineConfig } from "@trigger.dev/sdk";
  export default defineConfig({
  runtime: "node-24",
  project: "<your-project-ref>",
  });

• Avoid logging task run environment variable values at debug level (#4336)

• Updated dependencies:

  • @trigger.dev/[email protected]
  • @trigger.dev/[email protected]
  • @trigger.dev/[email protected]

... (truncated)

• 86b948b chore: release v4.5.9 (#4408)
• 878c158 fix(cli): redact environment values from build debug logs (#4420)
• 4eb9292 feat(webapp,run-engine): queue metrics and health dashboard (#4131)
• 38bf82a feat(cli,webapp): target notifications by minimum CLI version (#4407)
• d189ce1 chore: release v4.5.8 (#4364)
• aafc333 chore: release v4.5.7 (#4319)
• 55a3bf2 feat(core,cli): add node-24 and node-26 runtimes, deprecate experimental alia...
• 509a459 fix(cli): redact task run env values from debug log (#4336)
• a9815f7 fix(cli): stop dev runs crashing when a rebuild removes an in-use build dir (...
• dc87b88 chore: upgrade to typescript 6 (#4310)
• Additional commits viewable in compare view

This version was pushed to npm by GitHub Actions, a new releaser for trigger.dev since your current version.

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  You can disable automated security fix PRs for this repo from the Security Alerts page.