github-featured / triggerdotdev--trigger.dev

发布

0 发布 4,184 Git 标签

RSS 订阅源
  • v.docker.4.5.0-rc.5 a730faadfe
    比较

    chore: release v4.5.0-rc.5 (#3808)

    frostbyte_neo 发布于 2026-06-05 13:09:26 +00:00 | 747 次提交 在此版本后已推送到 main

    Summary

    1 new feature, 8 improvements, 1 bug fix.

    Highlights

    • Add optional shouldPauseScaling to the supervisor consumer pool
      scaling options to freeze scale-up while it returns true (scale-down
      stays allowed).
      (#3836)

    Improvements

    • The MCP server no longer tells the AI agent to wait for a run to
      complete after every trigger_task call. Waiting is now opt-in: the
      agent only waits when you ask it to (for example "trigger and then wait
      for it to finish"). This avoids burning tokens polling runs you didn't
      need to block on and keeps responses clearer.
      (#3838)
    • 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)
    • Adds AI SDK 7 support. The ai peer range now includes v7, and the
      chat.agent / chat surfaces work against v7's ESM-only build. On v7,
      install @ai-sdk/otel alongside ai and the SDK registers it for you
      so experimental_telemetry spans keep flowing into your run traces (v7
      stopped emitting them from ai core). v5 and v6 keep working unchanged.
      (#3833)
    • 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

    • The MCP server no longer tells the AI agent to wait for a run to
      complete after every trigger_task call. Waiting is now opt-in: the
      agent only waits when you ask it to (for example "trigger and then wait
      for it to finish"). This avoids burning tokens polling runs you didn't
      need to block on and keeps responses clearer.
      (#3838)
    • 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

    • Add optional shouldPauseScaling to the supervisor consumer pool
      scaling options to freeze scale-up while it returns true (scale-down
      stays allowed).
      (#3836)

    • 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

    • Adds AI SDK 7 support. The ai peer range now includes v7, and the
      chat.agent / chat surfaces work against v7's ESM-only build. On v7,
      install @ai-sdk/otel alongside ai and the SDK registers it for you
      so experimental_telemetry spans keep flowing into your run traces (v7
      stopped emitting them from ai core). v5 and v6 keep working unchanged.
      (#3833)

    • 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

    Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>

    下载附件