chore: release v4.4.7#3563
Open
github-actions[bot] wants to merge 1 commit into
Open
Conversation
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
1 improvement.
Improvements
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/build@4.4.7
Patch Changes
@trigger.dev/core@4.4.7trigger.dev@4.4.7
Patch Changes
@trigger.dev/core@4.4.7@trigger.dev/build@4.4.7@trigger.dev/schema-to-json@4.4.7@trigger.dev/core@4.4.7
Patch Changes
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)@trigger.dev/python@4.4.7
Patch Changes
@trigger.dev/core@4.4.7@trigger.dev/build@4.4.7@trigger.dev/sdk@4.4.7@trigger.dev/react-hooks@4.4.7
Patch Changes
@trigger.dev/core@4.4.7@trigger.dev/redis-worker@4.4.7
Patch Changes
@trigger.dev/core@4.4.7@trigger.dev/rsc@4.4.7
Patch Changes
@trigger.dev/core@4.4.7@trigger.dev/schema-to-json@4.4.7
Patch Changes
@trigger.dev/core@4.4.7@trigger.dev/sdk@4.4.7
Patch Changes
@trigger.dev/core@4.4.7