chore: release v4.5.0-rc.5

[github-actions]

Summary

6 improvements, 1 bug fix.

Improvements

• Update the bundled OpenTelemetry packages to their latest releases (@opentelemetry/sdk-node 0.218.0, @opentelemetry/core 2.7.1, @opentelemetry/host-metrics 0.38.3). (#3810)
• envvars.upload now accepts an optional isSecret flag, letting you create the imported variables as secret (redacted) environment variables. When omitted, variables default to non-secret. (#3809)
• Offload large trigger payloads to object storage before sending the trigger API request. The SDK uploads packets at or above the existing 128KB limit and sends an application/store pointer instead of embedding large JSON in the request body. TriggerTaskRequestBody now validates that application/store payloads are non-empty storage paths. (#3785)
• Make mollifier buffer and drainer internals configurable. MollifierBuffer now accepts ackGraceTtlSeconds, maxRetriesPerRequest, reconnectStepMs, and reconnectMaxMs options, and MollifierDrainer accepts maxBackoffMs and backoffFloorMs. All default to their previous hardcoded values, so existing behaviour is unchanged. (#3822)
• MollifierDrainer accepts a drainBatchSize option (default 1) that controls how many entries are popped per env per tick — in-flight handlers remain capped by the global concurrency. MollifierBuffer also gains getDrainingCount() / listStaleDraining(), backed by a new mollifier:draining ZSET maintained atomically with pop/ack/fail/requeue (observability-only). (#3797)
• useTriggerChatTransport now recovers when restored session state points at a session that no longer exists in the current environment (#3816)

Bug fixes

• Fix @trigger.dev/core build: cast the underlying log record exporter when calling forceFlush so it typechecks against the updated OpenTelemetry LogRecordExporter type (which no longer declares forceFlush). (#3829)

Raw changeset output

⚠️⚠️⚠️⚠️⚠️⚠️

main is currently in pre mode so this branch has prereleases rather than normal releases. If you want to exit prereleases, run changeset pre exit on main.

⚠️⚠️⚠️⚠️⚠️⚠️

Releases

@trigger.dev/build@4.5.0-rc.5

Patch Changes

• Updated dependencies:
  • @trigger.dev/core@4.5.0-rc.5

trigger.dev@4.5.0-rc.5

Patch Changes

• Update the bundled OpenTelemetry packages to their latest releases (@opentelemetry/sdk-node 0.218.0, @opentelemetry/core 2.7.1, @opentelemetry/host-metrics 0.38.3). (#3810)
• Updated dependencies:
  • @trigger.dev/core@4.5.0-rc.5
  • @trigger.dev/build@4.5.0-rc.5
  • @trigger.dev/schema-to-json@4.5.0-rc.5

@trigger.dev/core@4.5.0-rc.5

Patch Changes

• Fix @trigger.dev/core build: cast the underlying log record exporter when calling forceFlush so it typechecks against the updated OpenTelemetry LogRecordExporter type (which no longer declares forceFlush). (#3829)

• envvars.upload now accepts an optional isSecret flag, letting you create the imported variables as secret (redacted) environment variables. When omitted, variables default to non-secret. (#3809)

  await envvars.upload("proj_1234", "prod", {
    variables: { STRIPE_SECRET_KEY: "sk_live_..." },
    isSecret: true,
  });

• Offload large trigger payloads to object storage before sending the trigger API request. The SDK uploads packets at or above the existing 128KB limit and sends an application/store pointer instead of embedding large JSON in the request body. TriggerTaskRequestBody now validates that application/store payloads are non-empty storage paths. (#3785)

  Payload uploads use the same resolved ApiClient as the trigger call (including requestOptions.clientConfig), not only the global apiClientManager.client — so custom baseURL, access token, and preview branch apply to both presign and trigger.

• Update the bundled OpenTelemetry packages to their latest releases (@opentelemetry/sdk-node 0.218.0, @opentelemetry/core 2.7.1, @opentelemetry/host-metrics 0.38.3). (#3810)

@trigger.dev/plugins@4.5.0-rc.5

Patch Changes

• Updated dependencies:
  • @trigger.dev/core@4.5.0-rc.5

@trigger.dev/python@4.5.0-rc.5

Patch Changes

• Updated dependencies:
  • @trigger.dev/sdk@4.5.0-rc.5
  • @trigger.dev/core@4.5.0-rc.5
  • @trigger.dev/build@4.5.0-rc.5

@trigger.dev/react-hooks@4.5.0-rc.5

Patch Changes

• Updated dependencies:
  • @trigger.dev/core@4.5.0-rc.5

@trigger.dev/redis-worker@4.5.0-rc.5

Patch Changes

• Make mollifier buffer and drainer internals configurable. MollifierBuffer now accepts ackGraceTtlSeconds, maxRetriesPerRequest, reconnectStepMs, and reconnectMaxMs options, and MollifierDrainer accepts maxBackoffMs and backoffFloorMs. All default to their previous hardcoded values, so existing behaviour is unchanged. (#3822)
• MollifierDrainer accepts a drainBatchSize option (default 1) that controls how many entries are popped per env per tick — in-flight handlers remain capped by the global concurrency. MollifierBuffer also gains getDrainingCount() / listStaleDraining(), backed by a new mollifier:draining ZSET maintained atomically with pop/ack/fail/requeue (observability-only). (#3797)
• Updated dependencies:
  • @trigger.dev/core@4.5.0-rc.5

@trigger.dev/rsc@4.5.0-rc.5

Patch Changes

• Updated dependencies:
  • @trigger.dev/core@4.5.0-rc.5

@trigger.dev/schema-to-json@4.5.0-rc.5

Patch Changes

• Updated dependencies:
  • @trigger.dev/core@4.5.0-rc.5

@trigger.dev/sdk@4.5.0-rc.5

Patch Changes

• useTriggerChatTransport now recovers when restored session state points at a session that no longer exists in the current environment (#3816)

• Offload large trigger payloads to object storage before sending the trigger API request. The SDK uploads packets at or above the existing 128KB limit and sends an application/store pointer instead of embedding large JSON in the request body. TriggerTaskRequestBody now validates that application/store payloads are non-empty storage paths. (#3785)

  Payload uploads use the same resolved ApiClient as the trigger call (including requestOptions.clientConfig), not only the global apiClientManager.client — so custom baseURL, access token, and preview branch apply to both presign and trigger.

• Update the bundled OpenTelemetry packages to their latest releases (@opentelemetry/sdk-node 0.218.0, @opentelemetry/core 2.7.1, @opentelemetry/host-metrics 0.38.3). (#3810)

• Updated dependencies:

  • @trigger.dev/core@4.5.0-rc.5

[devin-ai-integration]

✅ Devin Review: No Issues Found

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

View in Devin Review to see 2 additional findings.

[devin-ai-integration]

Devin Review found 1 new potential issue.

[devin-ai-integration]

🚩 Removal of previously-consumed changesets from pre.json

Two changesets (mollifier-buffer-extensions, mollifier-drainer-terminal-failure-callback) that were consumed in rc.4 are being removed from pre.json's changesets array. Normally this array is append-only during a pre-release cycle. Investigation shows these changeset files were restored after rc.4 via commit 4c0c969f4 and then deleted again by PR #3797 (139eede41). The changesets CLI appears to have handled this edge case during changeset version, but it's worth verifying that the final stable release changelog will still include the rc.4 minor changes (mollifier buffer extensions and terminal failure callback) for @trigger.dev/redis-worker.

---

Was this helpful? React with 👍 or 👎 to provide feedback.