chore: release v4.5.12

[github-actions]

Summary

2 new features, 8 improvements, 8 bug fixes.

Highlights

• Define stable execution windows on declarative scheduled tasks. Schedule API responses now expose both the nominal CRON time and its assigned time, while the dashboard shows configured windows and upcoming assignments. (#4572)

Improvements

• New projects created with trigger init use Node.js 24 by default. Deployments without explicit runtime now use their project's configured default runtime. (#4649)
• Deployment builds now use custom base layer images and no longer install system packages during every build. This improves layer caching resulting in both faster deployments and faster image pulls on the worker cluster side. (#4602)
• Unrelated runs are no longer merged into a single trace in your external observability tool when they happen to execute on the same warm worker process. (#4534)
• Task metrics no longer go missing for projects that configure their own metricExporters or metricReaders, and the flush error that came with it is gone. (#4613)
• Fair queue tenants can no longer get permanently stuck behind leaked concurrency slots. Slots are now freed on every path that finishes a message, a failed release no longer causes a message to run twice or lose its retry, and a background sweep frees any slot that does leak, so a tenant's queues recover on their own instead of needing manual cleanup. (#4540)

Server changes

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

• Operators can now route an organization's runs to specific Kubernetes node pools. (#4655)
• Dashboard pages load faster on projects with many preview branches by no longer loading every environment on each page. (#4606)
• Global log search now supports faster bounded substring matching and clearer time-range expansion. (#4615)
• Triggering tasks is now more resilient to brief, transient service interruptions, so short stalls are less likely to surface as errors. (#4623)
• Failed AI SDK tool call and embedding spans now show the error message and stack trace in the run inspector, below the tool input. (#4653)
• Using * as a concurrency key no longer stops a queue from being processed. Triggering a single run with that key could leave the whole queue stalled, including runs using other concurrency keys on it, until something else was triggered on the same queue. (#4628)
• Fixed a brief window after promoting or rolling back a deployment where newly triggered runs could still execute on the previous version. New runs now pick up the current version immediately. (#4622)
• Root API keys no longer show an environment creation timestamp as their creation date. (#4612)
• The app version shown on the organization settings page now reports the real version instead of v0.0.0. (#4611)
• Fix paused environments starting to run work again after a deploy: a paused environment now stays paused until you resume it. (#4625)
• The "Back to app" button in organization settings now returns you to that organization instead of your most recently used one. (#4632)
• Runs triggered with a ttl could get permanently stuck in the queued state if they started executing and were then requeued after a failure (for example a worker dying mid-run) once the TTL had already elapsed. Requeued runs now dequeue normally: a run's TTL only applies while it is waiting to start for the first time. (#4669)

Raw changeset output

Releases

@trigger.dev/build@4.5.12

Patch Changes

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

trigger.dev@4.5.12

Patch Changes

• New projects created with trigger init use Node.js 24 by default. Deployments without explicit runtime now use their project's configured default runtime. (#4649)
• Deployment builds now use custom base layer images and no longer install system packages during every build. This improves layer caching resulting in both faster deployments and faster image pulls on the worker cluster side. (#4602)
• Updated dependencies:
  • @trigger.dev/core@4.5.12
  • @trigger.dev/build@4.5.12
  • @trigger.dev/schema-to-json@4.5.12

@trigger.dev/core@4.5.12

Patch Changes

• Unrelated runs are no longer merged into a single trace in your external observability tool when they happen to execute on the same warm worker process. (#4534)
• Task metrics no longer go missing for projects that configure their own metricExporters or metricReaders, and the flush error that came with it is gone. (#4613)
• Define stable execution windows on declarative scheduled tasks. Schedule API responses now expose both the nominal CRON time and its assigned time, while the dashboard shows configured windows and upcoming assignments. (#4572)

@trigger.dev/python@4.5.12

Patch Changes

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

@trigger.dev/react-hooks@4.5.12

Patch Changes

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

@trigger.dev/redis-worker@4.5.12

Patch Changes

• Fair queue tenants can no longer get permanently stuck behind leaked concurrency slots. Slots are now freed on every path that finishes a message, a failed release no longer causes a message to run twice or lose its retry, and a background sweep frees any slot that does leak, so a tenant's queues recover on their own instead of needing manual cleanup. (#4540)
• Updated dependencies:
  • @trigger.dev/core@4.5.12

@trigger.dev/rsc@4.5.12

Patch Changes

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

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

Patch Changes

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

@trigger.dev/sdk@4.5.12

Patch Changes

• Define stable execution windows on declarative scheduled tasks. Schedule API responses now expose both the nominal CRON time and its assigned time, while the dashboard shows configured windows and upcoming assignments. (#4572)
• Updated dependencies:
  • @trigger.dev/core@4.5.12

[devin-ai-integration]

✅ Devin Review: No Issues Found

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