github-featured/triggerdotdev--trigger.dev
2
0
Fork 0
Code Issues Pull Requests Deployments Models Agent Notes Packages Projects Releases Wiki Activity
Files
v.docker.4.4.6
triggerdotdev--trigger.dev/packages/python/CHANGELOG.md
T
github-actions[bot] 41a486ea7e
🚀 Publish Trigger.dev Docker / typecheck (push) Failing after 0s
Details
🚀 Publish Trigger.dev Docker / publish-webapp (push) Has been skipped
Details
🚀 Publish Trigger.dev Docker / publish-worker (push) Has been skipped
Details
🚀 Publish Trigger.dev Docker / publish-worker-v4 (push) Has been skipped
Details
🚀 Publish Trigger.dev Docker / units (push) Failing after 5s
Details
🧭 Helm Chart Release / lint-and-test (push) Has been cancelled
Details
🧭 Helm Chart Release / release (push) Has been cancelled
Details
chore: release v4.4.6 (#3501) 
## Summary
1 improvement, 1 bug fix.

## Improvements
- Fail attempts on uncaught exceptions instead of hanging to
`MAX_DURATION_EXCEEDED`. A Node `EventEmitter` (e.g. `node-redis`)
emitting `"error"` with no `.on("error", ...)` listener escalates to
`uncaughtException`, which the worker previously reported but did not
act on — runs drifted to maxDuration with empty attempts. They now fail
fast with the original error and status `FAILED`, and respect the task's
normal retry policy. You should still attach `.on("error", ...)`
listeners to long-lived clients to handle errors gracefully.
([#3529](https://github.com/triggerdotdev/trigger.dev/pull/3529))

## Bug fixes
- Fix dev workers spinning at 100% CPU after the parent CLI disconnects.
Orphaned `trigger-dev-run-worker` (and indexer) processes were caught in
an `uncaughtException` feedback loop: a periodic IPC send via
`process.send` would throw `ERR_IPC_CHANNEL_CLOSED` once the parent
closed the channel, which re-entered the same handler that itself called
`process.send`, scheduled via `setImmediate` and amplified by
source-map-support's `prepareStackTrace`. Fixed by (1) silently dropping
packets in `ZodIpcConnection` when the channel is disconnected, (2)
adding a `process.on("disconnect", ...)` handler in dev workers so they
exit cleanly when the CLI closes the IPC channel, and (3) wrapping all
`uncaughtException`-path `process.send` calls in a `safeSend` guard that
checks `process.connected` and swallows synchronous throws.
([#3491](https://github.com/triggerdotdev/trigger.dev/pull/3491))

<details>
<summary>Raw changeset output</summary>

# Releases
## @trigger.dev/build@4.4.6

### Patch Changes

-   Updated dependencies:
    -   `@trigger.dev/core@4.4.6`

## trigger.dev@4.4.6

### Patch Changes

- Fix dev workers spinning at 100% CPU after the parent CLI disconnects.
Orphaned `trigger-dev-run-worker` (and indexer) processes were caught in
an `uncaughtException` feedback loop: a periodic IPC send via
`process.send` would throw `ERR_IPC_CHANNEL_CLOSED` once the parent
closed the channel, which re-entered the same handler that itself called
`process.send`, scheduled via `setImmediate` and amplified by
source-map-support's `prepareStackTrace`. Fixed by (1) silently dropping
packets in `ZodIpcConnection` when the channel is disconnected, (2)
adding a `process.on("disconnect", ...)` handler in dev workers so they
exit cleanly when the CLI closes the IPC channel, and (3) wrapping all
`uncaughtException`-path `process.send` calls in a `safeSend` guard that
checks `process.connected` and swallows synchronous throws.
([#3491](https://github.com/triggerdotdev/trigger.dev/pull/3491))
- Fail attempts on uncaught exceptions instead of hanging to
`MAX_DURATION_EXCEEDED`. A Node `EventEmitter` (e.g. `node-redis`)
emitting `"error"` with no `.on("error", ...)` listener escalates to
`uncaughtException`, which the worker previously reported but did not
act on — runs drifted to maxDuration with empty attempts. They now fail
fast with the original error and status `FAILED`, and respect the task's
normal retry policy. You should still attach `.on("error", ...)`
listeners to long-lived clients to handle errors gracefully.
([#3529](https://github.com/triggerdotdev/trigger.dev/pull/3529))
-   Updated dependencies:
    -   `@trigger.dev/core@4.4.6`
    -   `@trigger.dev/build@4.4.6`
    -   `@trigger.dev/schema-to-json@4.4.6`

## @trigger.dev/core@4.4.6

### Patch Changes

- Fix dev workers spinning at 100% CPU after the parent CLI disconnects.
Orphaned `trigger-dev-run-worker` (and indexer) processes were caught in
an `uncaughtException` feedback loop: a periodic IPC send via
`process.send` would throw `ERR_IPC_CHANNEL_CLOSED` once the parent
closed the channel, which re-entered the same handler that itself called
`process.send`, scheduled via `setImmediate` and amplified by
source-map-support's `prepareStackTrace`. Fixed by (1) silently dropping
packets in `ZodIpcConnection` when the channel is disconnected, (2)
adding a `process.on("disconnect", ...)` handler in dev workers so they
exit cleanly when the CLI closes the IPC channel, and (3) wrapping all
`uncaughtException`-path `process.send` calls in a `safeSend` guard that
checks `process.connected` and swallows synchronous throws.
([#3491](https://github.com/triggerdotdev/trigger.dev/pull/3491))
- Fail attempts on uncaught exceptions instead of hanging to
`MAX_DURATION_EXCEEDED`. A Node `EventEmitter` (e.g. `node-redis`)
emitting `"error"` with no `.on("error", ...)` listener escalates to
`uncaughtException`, which the worker previously reported but did not
act on — runs drifted to maxDuration with empty attempts. They now fail
fast with the original error and status `FAILED`, and respect the task's
normal retry policy. You should still attach `.on("error", ...)`
listeners to long-lived clients to handle errors gracefully.
([#3529](https://github.com/triggerdotdev/trigger.dev/pull/3529))

## @trigger.dev/python@4.4.6

### Patch Changes

-   Updated dependencies:
    -   `@trigger.dev/core@4.4.6`
    -   `@trigger.dev/build@4.4.6`
    -   `@trigger.dev/sdk@4.4.6`

## @trigger.dev/react-hooks@4.4.6

### Patch Changes

-   Updated dependencies:
    -   `@trigger.dev/core@4.4.6`

## @trigger.dev/redis-worker@4.4.6

### Patch Changes

-   Updated dependencies:
    -   `@trigger.dev/core@4.4.6`

## @trigger.dev/rsc@4.4.6

### Patch Changes

-   Updated dependencies:
    -   `@trigger.dev/core@4.4.6`

## @trigger.dev/schema-to-json@4.4.6

### Patch Changes

-   Updated dependencies:
    -   `@trigger.dev/core@4.4.6`

## @trigger.dev/sdk@4.4.6

### Patch Changes

-   Updated dependencies:
    -   `@trigger.dev/core@4.4.6`

</details>

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
2026-05-12 11:33:00 +01:00

9.3 KiB
Raw Permalink Blame History

@trigger.dev/python

4.4.6

Patch Changes

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

4.4.5

Patch Changes

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

4.4.4

Patch Changes

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

4.4.3

Patch Changes

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

4.4.2

Patch Changes

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

4.4.1

Patch Changes

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

4.4.0

Patch Changes

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

4.3.3

Patch Changes

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

4.3.2

Patch Changes

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

4.3.1

Patch Changes

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

4.3.0

Patch Changes

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

4.2.0

Patch Changes

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

4.1.2

Patch Changes

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

4.1.1

Patch Changes

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

4.1.0

Patch Changes

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

4.0.7

Patch Changes

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

4.0.6

Patch Changes

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

4.0.5

Patch Changes

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

4.0.4

Patch Changes

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

4.0.3

Patch Changes

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

4.0.2

Patch Changes

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

4.0.1

Patch Changes

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

4.0.0

Major Changes

Patch Changes

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

4.0.0-v4-beta.28

Patch Changes

  • Updated dependencies:
    • @trigger.dev/sdk@4.0.0-v4-beta.28
    • @trigger.dev/core@4.0.0-v4-beta.28
    • @trigger.dev/build@4.0.0-v4-beta.28

4.0.0-v4-beta.27

Patch Changes

  • Updated dependencies:
    • @trigger.dev/sdk@4.0.0-v4-beta.27
    • @trigger.dev/build@4.0.0-v4-beta.27
    • @trigger.dev/core@4.0.0-v4-beta.27

4.0.0-v4-beta.26

Patch Changes

  • Updated dependencies:
    • @trigger.dev/sdk@4.0.0-v4-beta.26
    • @trigger.dev/build@4.0.0-v4-beta.26
    • @trigger.dev/core@4.0.0-v4-beta.26

4.0.0-v4-beta.25

Patch Changes

  • Updated dependencies:
    • @trigger.dev/build@4.0.0-v4-beta.25
    • @trigger.dev/core@4.0.0-v4-beta.25
    • @trigger.dev/sdk@4.0.0-v4-beta.25

4.0.0-v4-beta.24

Patch Changes

  • Updated dependencies:
    • @trigger.dev/sdk@4.0.0-v4-beta.24
    • @trigger.dev/build@4.0.0-v4-beta.24
    • @trigger.dev/core@4.0.0-v4-beta.24

4.0.0-v4-beta.23

Patch Changes

  • Updated dependencies:
    • @trigger.dev/sdk@4.0.0-v4-beta.23
    • @trigger.dev/core@4.0.0-v4-beta.23
    • @trigger.dev/build@4.0.0-v4-beta.23

4.0.0-v4-beta.22

Patch Changes

  • Updated dependencies:
    • @trigger.dev/core@4.0.0-v4-beta.22
    • @trigger.dev/sdk@4.0.0-v4-beta.22
    • @trigger.dev/build@4.0.0-v4-beta.22

4.0.0-v4-beta.21

Patch Changes

  • Updated dependencies:
    • @trigger.dev/core@4.0.0-v4-beta.21
    • @trigger.dev/build@4.0.0-v4-beta.21
    • @trigger.dev/sdk@4.0.0-v4-beta.21

4.0.0-v4-beta.20

Patch Changes

  • Updated dependencies:
    • @trigger.dev/build@4.0.0-v4-beta.20
    • @trigger.dev/core@4.0.0-v4-beta.20
    • @trigger.dev/sdk@4.0.0-v4-beta.20

4.0.0-v4-beta.19

Patch Changes

  • Updated dependencies:
    • @trigger.dev/core@4.0.0-v4-beta.19
    • @trigger.dev/sdk@4.0.0-v4-beta.19
    • @trigger.dev/build@4.0.0-v4-beta.19

4.0.0-v4-beta.18

Patch Changes

  • Updated dependencies:
    • @trigger.dev/build@4.0.0-v4-beta.18
    • @trigger.dev/core@4.0.0-v4-beta.18
    • @trigger.dev/sdk@4.0.0-v4-beta.18

4.0.0-v4-beta.17

Patch Changes

  • Updated dependencies:
    • @trigger.dev/core@4.0.0-v4-beta.17
    • @trigger.dev/build@4.0.0-v4-beta.17
    • @trigger.dev/sdk@4.0.0-v4-beta.17

4.0.0-v4-beta.16

Patch Changes

  • Updated dependencies:
    • @trigger.dev/build@4.0.0-v4-beta.16
    • @trigger.dev/core@4.0.0-v4-beta.16
    • @trigger.dev/sdk@4.0.0-v4-beta.16

4.0.0-v4-beta.15

Patch Changes

  • Updated dependencies:
    • @trigger.dev/build@4.0.0-v4-beta.15
    • @trigger.dev/core@4.0.0-v4-beta.15
    • @trigger.dev/sdk@4.0.0-v4-beta.15

4.0.0-v4-beta.14

Patch Changes

  • Updated dependencies:
    • @trigger.dev/sdk@4.0.0-v4-beta.14
    • @trigger.dev/build@4.0.0-v4-beta.14
    • @trigger.dev/core@4.0.0-v4-beta.14

4.0.0-v4-beta.13

Patch Changes

  • Updated dependencies:
    • @trigger.dev/core@4.0.0-v4-beta.13
    • @trigger.dev/build@4.0.0-v4-beta.13
    • @trigger.dev/sdk@4.0.0-v4-beta.13

4.0.0-v4-beta.12

Patch Changes

  • Updated dependencies:
    • @trigger.dev/sdk@4.0.0-v4-beta.12
    • @trigger.dev/build@4.0.0-v4-beta.12
    • @trigger.dev/core@4.0.0-v4-beta.12

4.0.0-v4-beta.11

Patch Changes

  • Updated dependencies:
    • @trigger.dev/sdk@4.0.0-v4-beta.11
    • @trigger.dev/build@4.0.0-v4-beta.11
    • @trigger.dev/core@4.0.0-v4-beta.11

4.0.0-v4-beta.10

Patch Changes

  • Updated dependencies:
    • @trigger.dev/core@4.0.0-v4-beta.10
    • @trigger.dev/build@4.0.0-v4-beta.10
    • @trigger.dev/sdk@4.0.0-v4-beta.10

4.0.0-v4-beta.9

Patch Changes

  • Updated dependencies:
    • @trigger.dev/build@4.0.0-v4-beta.9
    • @trigger.dev/core@4.0.0-v4-beta.9
    • @trigger.dev/sdk@4.0.0-v4-beta.9

4.0.0-v4-beta.8

Patch Changes

  • Updated dependencies:
    • @trigger.dev/core@4.0.0-v4-beta.8
    • @trigger.dev/build@4.0.0-v4-beta.8
    • @trigger.dev/sdk@4.0.0-v4-beta.8

4.0.0-v4-beta.7

Patch Changes

  • Updated dependencies:
    • @trigger.dev/core@4.0.0-v4-beta.7
    • @trigger.dev/build@4.0.0-v4-beta.7
    • @trigger.dev/sdk@4.0.0-v4-beta.7

4.0.0-v4-beta.6

Patch Changes

  • Updated dependencies:
    • @trigger.dev/core@4.0.0-v4-beta.6
    • @trigger.dev/sdk@4.0.0-v4-beta.6
    • @trigger.dev/build@4.0.0-v4-beta.6

4.0.0-v4-beta.5

Patch Changes

  • Updated dependencies:
    • @trigger.dev/sdk@4.0.0-v4-beta.5
    • @trigger.dev/build@4.0.0-v4-beta.5
    • @trigger.dev/core@4.0.0-v4-beta.5

4.0.0-v4-beta.4

Patch Changes

  • Updated dependencies:
    • @trigger.dev/sdk@4.0.0-v4-beta.4
    • @trigger.dev/build@4.0.0-v4-beta.4
    • @trigger.dev/core@4.0.0-v4-beta.4

4.0.0-v4-beta.3

Patch Changes

  • Updated dependencies:
    • @trigger.dev/core@4.0.0-v4-beta.3
    • @trigger.dev/build@4.0.0-v4-beta.3
    • @trigger.dev/sdk@4.0.0-v4-beta.3

4.0.0-v4-beta.2

Patch Changes

  • Updated dependencies:
    • @trigger.dev/core@4.0.0-v4-beta.2
    • @trigger.dev/build@4.0.0-v4-beta.2
    • @trigger.dev/sdk@4.0.0-v4-beta.2

4.0.0-v4-beta.1

Patch Changes

  • Updated dependencies:
    • @trigger.dev/build@4.0.0-v4-beta.1
    • @trigger.dev/core@4.0.0-v4-beta.1
    • @trigger.dev/sdk@4.0.0-v4-beta.1

4.0.0-v4-beta.0

Major Changes

Patch Changes

  • Updated dependencies:
    • @trigger.dev/sdk@4.0.0-v4-beta.0
    • @trigger.dev/build@4.0.0-v4-beta.0
    • @trigger.dev/core@4.0.0-v4-beta.0

3.3.17

Patch Changes

  • Introduced a new Python extension to enhance the build process. It now allows users to execute Python scripts with improved support and error handling. (#1686)
  • Updated dependencies:
    • @trigger.dev/sdk@3.3.17
    • @trigger.dev/core@3.3.17
    • @trigger.dev/build@3.3.17
Reference in New Issue View Git Blame Copy Permalink