chore: release v4.4.4

[github-actions]

Summary

2 new features, 43 improvements, 14 bug fixes.

Improvements

• get_query_schema — discover available TRQL tables and columns
• query — execute TRQL queries against your data
• list_dashboards — list built-in dashboards and their widgets
• run_dashboard_query — execute a single dashboard widget query
• whoami — show current profile, user, and API URL
• list_profiles — list all configured CLI profiles
• switch_profile — switch active profile for the MCP session
• start_dev_server — start trigger dev in the background and stream output
• stop_dev_server — stop the running dev server
• dev_server_status — check dev server status and view recent logs
• GET /api/v1/query/schema — query table schema discovery
• GET /api/v1/query/dashboards — list built-in dashboards
• --readonly flag hides write tools (deploy, trigger_task, cancel_run) so the AI cannot make changes
• read:query JWT scope for query endpoint authorization
• get_run_details trace output is now paginated with cursor support
• MCP tool annotations (readOnlyHint, destructiveHint) for all tools
• get_query_schema now requires a table name and returns only one table's schema (was returning all tables)
• get_current_worker no longer inlines payload schemas; use new get_task_schema tool instead
• Query results formatted as text tables instead of JSON (~50% fewer tokens)
• cancel_run, list_deploys, list_preview_branches formatted as text instead of raw JSON
• Schema and dashboard API responses cached to avoid redundant fetches
• Propagate run tags to span attributes so they can be extracted server-side for LLM cost attribution metadata. (#3213)
• get_query_schema — discover available TRQL tables and columns
• query — execute TRQL queries against your data
• list_dashboards — list built-in dashboards and their widgets
• run_dashboard_query — execute a single dashboard widget query
• whoami — show current profile, user, and API URL
• list_profiles — list all configured CLI profiles
• switch_profile — switch active profile for the MCP session
• start_dev_server — start trigger dev in the background and stream output
• stop_dev_server — stop the running dev server
• dev_server_status — check dev server status and view recent logs
• GET /api/v1/query/schema — query table schema discovery
• GET /api/v1/query/dashboards — list built-in dashboards
• --readonly flag hides write tools (deploy, trigger_task, cancel_run) so the AI cannot make changes
• read:query JWT scope for query endpoint authorization
• get_run_details trace output is now paginated with cursor support
• MCP tool annotations (readOnlyHint, destructiveHint) for all tools
• get_query_schema now requires a table name and returns only one table's schema (was returning all tables)
• get_current_worker no longer inlines payload schemas; use new get_task_schema tool instead
• Query results formatted as text tables instead of JSON (~50% fewer tokens)
• cancel_run, list_deploys, list_preview_branches formatted as text instead of raw JSON
• Schema and dashboard API responses cached to avoid redundant fetches

Bug fixes

• Fix dev CLI leaking build directories on rebuild, causing disk space accumulation. Deprecated workers are now pruned (capped at 2 retained) when no active runs reference them. The watchdog process also cleans up .trigger/tmp/ when the dev CLI is killed ungracefully (e.g. SIGKILL from pnpm). (#3224)
• Fixed search_docs tool failing due to renamed upstream Mintlify tool (SearchTriggerDev → search_trigger_dev)
• Fixed list_deploys failing when deployments have null runtime/runtimeVersion fields (MCP server: list_deploys fails with validation error on null runtime/runtimeVersion #3139)
• Fixed list_preview_branches crashing due to incorrect response shape access
• Fixed metrics table column documented as value instead of metric_value in query docs
• Fixed dev CLI leaking build directories on rebuild — deprecated workers now clean up their build dirs when their last run completes
• Fixed search_docs tool failing due to renamed upstream Mintlify tool (SearchTriggerDev → search_trigger_dev)
• Fixed list_deploys failing when deployments have null runtime/runtimeVersion fields (MCP server: list_deploys fails with validation error on null runtime/runtimeVersion #3139)
• Fixed list_preview_branches crashing due to incorrect response shape access
• Fixed metrics table column documented as value instead of metric_value in query docs
• Fixed dev CLI leaking build directories on rebuild — deprecated workers now clean up their build dirs when their last run completes

Server changes

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

• Add allowRollbacks query param to the promote deployment API to enable version downgrades (#3214)
• Add automatic LLM cost calculation for spans with GenAI semantic conventions. When a span arrives with gen_ai.response.model and token usage data, costs are calculated from an in-memory pricing registry backed by Postgres and dual-written to both span attributes (trigger.llm.*) and a new llm_metrics_v1 ClickHouse table that captures usage, cost, performance (TTFC, tokens/sec), and behavioral (finish reason, operation type) metrics. (#3213)
• Concurrency-keyed queues now use a single master queue entry per base queue instead of one entry per key. Prevents high-CK-count tenants from consuming the entire parentQueueLimit window and starving other tenants on the same shard. (#3219)
• Reduce lock contention when processing large batchTriggerAndWait batches. Previously, each batch item acquired a Redis lock on the parent run to insert a TaskRunWaitpoint row, causing LockAcquisitionTimeoutError with high concurrency (880 errors/24h in prod). Since blockRunWithCreatedBatch already transitions the parent to EXECUTING_WITH_WAITPOINTS before items are processed, the per-item lock is unnecessary. The new blockRunWithWaitpointLockless method performs only the idempotent CTE insert without acquiring the lock. (#3232)
• Strip secure query parameter from QUERY_CLICKHOUSE_URL before passing to ClickHouse client. This was already done for the main and logs ClickHouse clients but was missing for the query client, causing a startup crash with Error: Unknown URL parameters: secure. (#3204)

Raw changeset output

Releases

@trigger.dev/build@4.4.4

Patch Changes

• Updated dependencies:
  • @trigger.dev/core@4.4.4

trigger.dev@4.4.4

Patch Changes

• Fix dev CLI leaking build directories on rebuild, causing disk space accumulation. Deprecated workers are now pruned (capped at 2 retained) when no active runs reference them. The watchdog process also cleans up .trigger/tmp/ when the dev CLI is killed ungracefully (e.g. SIGKILL from pnpm). (#3224)

• MCP server improvements: new tools, bug fixes, and new flags. (#3224)

  New tools:

  • get_query_schema — discover available TRQL tables and columns
  • query — execute TRQL queries against your data
  • list_dashboards — list built-in dashboards and their widgets
  • run_dashboard_query — execute a single dashboard widget query
  • whoami — show current profile, user, and API URL
  • list_profiles — list all configured CLI profiles
  • switch_profile — switch active profile for the MCP session
  • start_dev_server — start trigger dev in the background and stream output
  • stop_dev_server — stop the running dev server
  • dev_server_status — check dev server status and view recent logs

  New API endpoints:

  • GET /api/v1/query/schema — query table schema discovery
  • GET /api/v1/query/dashboards — list built-in dashboards

  New features:

  • --readonly flag hides write tools (deploy, trigger_task, cancel_run) so the AI cannot make changes
  • read:query JWT scope for query endpoint authorization
  • get_run_details trace output is now paginated with cursor support
  • MCP tool annotations (readOnlyHint, destructiveHint) for all tools

  Bug fixes:

  • Fixed search_docs tool failing due to renamed upstream Mintlify tool (SearchTriggerDev → search_trigger_dev)
  • Fixed list_deploys failing when deployments have null runtime/runtimeVersion fields (MCP server: list_deploys fails with validation error on null runtime/runtimeVersion #3139)
  • Fixed list_preview_branches crashing due to incorrect response shape access
  • Fixed metrics table column documented as value instead of metric_value in query docs
  • Fixed dev CLI leaking build directories on rebuild — deprecated workers now clean up their build dirs when their last run completes

  Context optimizations:

  • get_query_schema now requires a table name and returns only one table's schema (was returning all tables)
  • get_current_worker no longer inlines payload schemas; use new get_task_schema tool instead
  • Query results formatted as text tables instead of JSON (~50% fewer tokens)
  • cancel_run, list_deploys, list_preview_branches formatted as text instead of raw JSON
  • Schema and dashboard API responses cached to avoid redundant fetches

• Updated dependencies:

  • @trigger.dev/core@4.4.4
  • @trigger.dev/build@4.4.4
  • @trigger.dev/schema-to-json@4.4.4

@trigger.dev/core@4.4.4

Patch Changes

• Fix list_deploys MCP tool failing when deployments have null runtime or runtimeVersion fields. (#3224)

• Propagate run tags to span attributes so they can be extracted server-side for LLM cost attribution metadata. (#3213)

• MCP server improvements: new tools, bug fixes, and new flags. (#3224)

  New tools:

  • get_query_schema — discover available TRQL tables and columns
  • query — execute TRQL queries against your data
  • list_dashboards — list built-in dashboards and their widgets
  • run_dashboard_query — execute a single dashboard widget query
  • whoami — show current profile, user, and API URL
  • list_profiles — list all configured CLI profiles
  • switch_profile — switch active profile for the MCP session
  • start_dev_server — start trigger dev in the background and stream output
  • stop_dev_server — stop the running dev server
  • dev_server_status — check dev server status and view recent logs

  New API endpoints:

  • GET /api/v1/query/schema — query table schema discovery
  • GET /api/v1/query/dashboards — list built-in dashboards

  New features:

  • --readonly flag hides write tools (deploy, trigger_task, cancel_run) so the AI cannot make changes
  • read:query JWT scope for query endpoint authorization
  • get_run_details trace output is now paginated with cursor support
  • MCP tool annotations (readOnlyHint, destructiveHint) for all tools

  Bug fixes:

  • Fixed search_docs tool failing due to renamed upstream Mintlify tool (SearchTriggerDev → search_trigger_dev)
  • Fixed list_deploys failing when deployments have null runtime/runtimeVersion fields (MCP server: list_deploys fails with validation error on null runtime/runtimeVersion #3139)
  • Fixed list_preview_branches crashing due to incorrect response shape access
  • Fixed metrics table column documented as value instead of metric_value in query docs
  • Fixed dev CLI leaking build directories on rebuild — deprecated workers now clean up their build dirs when their last run completes

  Context optimizations:

  • get_query_schema now requires a table name and returns only one table's schema (was returning all tables)
  • get_current_worker no longer inlines payload schemas; use new get_task_schema tool instead
  • Query results formatted as text tables instead of JSON (~50% fewer tokens)
  • cancel_run, list_deploys, list_preview_branches formatted as text instead of raw JSON
  • Schema and dashboard API responses cached to avoid redundant fetches

@trigger.dev/python@4.4.4

Patch Changes

• Updated dependencies:
  • @trigger.dev/core@4.4.4
  • @trigger.dev/build@4.4.4
  • @trigger.dev/sdk@4.4.4

@trigger.dev/react-hooks@4.4.4

Patch Changes

• Updated dependencies:
  • @trigger.dev/core@4.4.4

@trigger.dev/redis-worker@4.4.4

Patch Changes

• Updated dependencies:
  • @trigger.dev/core@4.4.4

@trigger.dev/rsc@4.4.4

Patch Changes

• Updated dependencies:
  • @trigger.dev/core@4.4.4

@trigger.dev/schema-to-json@4.4.4

Patch Changes

• Updated dependencies:
  • @trigger.dev/core@4.4.4

@trigger.dev/sdk@4.4.4

Patch Changes

• Updated dependencies:
  • @trigger.dev/core@4.4.4

[devin-ai-integration]

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no bugs or issues to report.

[devin-ai-integration]

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no bugs or issues to report.