chore: release v4.5.4

[github-actions]

Summary

1 new feature, 3 improvements, 3 bug fixes.

Improvements

• You can now mark environment variables synced via the syncEnvVars build extension as secrets. Return { name, value, isSecret: true } from your callback and those variables are stored redacted in the dashboard, just like manually created secret env vars. (#4203)

Server changes

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

• Promo credits: a /promo signup landing page, redeeming a promo code when a new org selects a plan, and showing remaining credits on the usage page. (#4138)
• Clearer login error when an email address is blocked by the WHITELISTED_EMAILS setting: the message now explains the address isn't allowed on this instance instead of the ambiguous "This email is unauthorized". (#4220)
• Clarified on the Regions page that a region only affects where your runs execute, not where your data is stored. This shows as a tooltip on the Location column and in the confirmation dialog when you change your default region. (#4226)
• Fixed stale login errors: an error from a previous login attempt (for example a rejected email address) no longer keeps reappearing on the login page and no longer makes later, successful attempts look like they failed. (#4220)
• The Errors page now shows better details for each error. Errors that don't carry a message — such as errors thrown without a message, or values thrown that aren't Error objects — get a meaningful title instead of all reading "Unknown error", and are grouped by their name (or value) rather than collapsed into a single group. The error type now shows the actual error name, and stack traces now appear where previously they were missing. (#4225)
• Query page: extracting fields from a run's output with JSON functions (such as JSONExtractString or JSONExtractInt) no longer fails with an "illegal type: JSON" error. (#4221)

Raw changeset output

Releases

@trigger.dev/build@4.5.4

Patch Changes

• You can now mark environment variables synced via the syncEnvVars build extension as secrets. Return { name, value, isSecret: true } from your callback and those variables are stored redacted in the dashboard, just like manually created secret env vars. (#4203)
• Updated dependencies:
  • @trigger.dev/core@4.5.4

trigger.dev@4.5.4

Patch Changes

• Updated dependencies:
  • @trigger.dev/build@4.5.4
  • @trigger.dev/core@4.5.4
  • @trigger.dev/schema-to-json@4.5.4

@trigger.dev/python@4.5.4

Patch Changes

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

@trigger.dev/react-hooks@4.5.4

Patch Changes

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

@trigger.dev/redis-worker@4.5.4

Patch Changes

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

@trigger.dev/rsc@4.5.4

Patch Changes

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

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

Patch Changes

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

@trigger.dev/sdk@4.5.4

Patch Changes

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

@trigger.dev/core@4.5.4

[devin-ai-integration]

✅ Devin Review: No Issues Found

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