chore: release v4.5.0#3563
Open
github-actions[bot] wants to merge 1 commit into
Open
Conversation
28fd35c to
9a0e7f8
Compare
9a0e7f8 to
e477aeb
Compare
e477aeb to
2dd9063
Compare
2dd9063 to
7390aa8
Compare
7390aa8 to
48d6326
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
4 improvements.
Improvements
idempotencyKeyvalues at the API boundary so they no longer trip an internal size limit on the underlying unique index and surface as a generic 500. Inputs are capped at 2048 characters — well above whatidempotencyKeys.create()produces (a 64-character hash) and above any realistic raw key. Applies totasks.trigger,tasks.batchTrigger,batch.create(Phase 1 streaming batches),wait.createToken,wait.forDuration, and the input/session stream waitpoint endpoints. Over-limit requests now return a structured 400 instead. (#3560)TASK_PROCESS_SIGSEGVtask crashes under the user's retry policy instead of failing the run on the first segfault. SIGSEGV in Node tasks is frequently non-deterministic (native addon races, JIT/GC interaction, near-OOM in native code, host issues), so retrying on a fresh process often succeeds. The retry is gated by the task's existingretryconfig +maxAttempts— same pathTASK_PROCESS_SIGTERMand uncaught exceptions already use — so tasks without a retry policy still fail fast. (#3552)Raw changeset output
Releases
@trigger.dev/sdk@4.5.0
Minor Changes
on a stable
externalId. Public SDK additions:tasks.triggerAndSubscribe()and the
chat.agentruntime built on top of Sessions. Seehttps://trigger.dev/docs/ai-chat/overview for the full feature surface.
Patch Changes
@trigger.dev/core@4.5.0@trigger.dev/build@4.5.0
Patch Changes
@trigger.dev/core@4.5.0trigger.dev@4.5.0
Patch Changes
@trigger.dev/core@4.5.0@trigger.dev/build@4.5.0@trigger.dev/schema-to-json@4.5.0@trigger.dev/core@4.5.0
Patch Changes
idempotencyKeyvalues at the API boundary so they no longer trip an internal size limit on the underlying unique index and surface as a generic 500. Inputs are capped at 2048 characters — well above whatidempotencyKeys.create()produces (a 64-character hash) and above any realistic raw key. Applies totasks.trigger,tasks.batchTrigger,batch.create(Phase 1 streaming batches),wait.createToken,wait.forDuration, and the input/session stream waitpoint endpoints. Over-limit requests now return a structured 400 instead. (#3560)ChatChunkTooLargeErrorand ApiClient methods for subscribing to session streams. Lays the groundwork for the upcomingchat.agent. (#3542)TASK_PROCESS_SIGSEGVtask crashes under the user's retry policy instead of failing the run on the first segfault. SIGSEGV in Node tasks is frequently non-deterministic (native addon races, JIT/GC interaction, near-OOM in native code, host issues), so retrying on a fresh process often succeeds. The retry is gated by the task's existingretryconfig +maxAttempts— same pathTASK_PROCESS_SIGTERMand uncaught exceptions already use — so tasks without a retry policy still fail fast. (#3552)on a stable
externalId. Public SDK additions:tasks.triggerAndSubscribe()and the
chat.agentruntime built on top of Sessions. Seehttps://trigger.dev/docs/ai-chat/overview for the full feature surface.
@trigger.dev/plugins@4.5.0
Patch Changes
@trigger.dev/core@4.5.0@trigger.dev/python@4.5.0
Patch Changes
@trigger.dev/core@4.5.0@trigger.dev/sdk@4.5.0@trigger.dev/build@4.5.0@trigger.dev/react-hooks@4.5.0
Patch Changes
@trigger.dev/core@4.5.0@trigger.dev/redis-worker@4.5.0
Patch Changes
@trigger.dev/core@4.5.0@trigger.dev/rsc@4.5.0
Patch Changes
@trigger.dev/core@4.5.0@trigger.dev/schema-to-json@4.5.0
Patch Changes
@trigger.dev/core@4.5.0