github-featured/triggerdotdev--trigger.dev
2
0
Fork 0
Code Issues Pull Requests Deployments Models Agent Notes Packages Projects Releases Wiki Activity
Files
054bb3224971ee741cf519af0a257564b565556a
triggerdotdev--trigger.dev/packages/python/CHANGELOG.md
T
github-actions[bot] f8aacacb8f chore: release v4.5.14 (#4813) 
## Summary
4 improvements, 1 bug fix.

## Improvements
- Native build server deploys now show a single updating build log line
by default; pass `--build-logs full` to stream every line (always used
in CI and when output is not a terminal).
([#4817](https://github.com/triggerdotdev/trigger.dev/pull/4817))
- Realtime stream subscriptions can now refresh an expired access token
and reconnect, via a new optional `refreshAccessToken` option on the
client configuration and the React hooks.
([#4811](https://github.com/triggerdotdev/trigger.dev/pull/4811))
- Subscribe to a realtime stream from its latest record instead of
replaying the whole history. Pass `from: "latest"` to
`useRealtimeStream`, `streams.read()`, or `fetchStream` to start at the
current tail (the latest record, then live updates) instead of replaying
(a live "last value" view), and `maxParts` to keep the accumulated
`parts` array bounded. A reconnect or remount resumes from the last
record it saw, so no records are missed and none are replayed. `from:
"latest"` needs a server that supports it; older servers safely fall
back to a full replay.
([#4811](https://github.com/triggerdotdev/trigger.dev/pull/4811))
  
`useRealtimeStream` also gains a `lastEventId` option and returns the
`lastEventId` of the last part seen, so you can persist the cursor (for
example across a page reload) and resume exactly where you left off. An
`onParts` callback delivers each throttled batch of parts with their
event ids.
  
  ```tsx
const { parts, lastEventId } = useRealtimeStream<Frame>(runId, "frames",
{
  from: "latest", // skip history, start at the current tail
  maxParts: 1, // keep only the most recent frame
  lastEventId: savedCursor, // resume from a persisted cursor
  onParts: (batch) => save(batch.at(-1)?.id), // track the cursor
  accessToken,
  });
  ```
- Added a `useSessionStream` React hook for reading a session's output
or input channel in realtime. It accumulates records with automatic
resume from the last record you received, and supports `from: "latest"`
(start at the current tail, only new records after you connect),
`maxRecords` (keep a bounded number of records in memory), a
`lastEventId` resume cursor, and an `onRecords` callback that delivers
each throttled batch of records with their event ids.
([#4811](https://github.com/triggerdotdev/trigger.dev/pull/4811))

## Server changes

These changes affect the self-hosted Docker image and Trigger.dev Cloud:

- Task retries that wait in the queue no longer count against the
queue's internal redelivery limit, so runs with many long-delay retries
are not wrongly failed with TASK_RUN_DEQUEUED_MAX_RETRIES.
([#4810](https://github.com/triggerdotdev/trigger.dev/pull/4810))

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

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

### Patch Changes

- Updated dependencies:
  - `@trigger.dev/core@4.5.14`
## trigger.dev@4.5.14

### Patch Changes

- Native build server deploys now show a single updating build log line
by default; pass `--build-logs full` to stream every line (always used
in CI and when output is not a terminal).
([#4817](https://github.com/triggerdotdev/trigger.dev/pull/4817))
- Updated dependencies:
  - `@trigger.dev/core@4.5.14`
  - `@trigger.dev/build@4.5.14`
  - `@trigger.dev/schema-to-json@4.5.14`
## @trigger.dev/core@4.5.14

### Patch Changes

- Realtime stream subscriptions can now refresh an expired access token
and reconnect, via a new optional `refreshAccessToken` option on the
client configuration and the React hooks.
([#4811](https://github.com/triggerdotdev/trigger.dev/pull/4811))
- Subscribe to a realtime stream from its latest record instead of
replaying the whole history. Pass `from: "latest"` to
`useRealtimeStream`, `streams.read()`, or `fetchStream` to start at the
current tail (the latest record, then live updates) instead of replaying
(a live "last value" view), and `maxParts` to keep the accumulated
`parts` array bounded. A reconnect or remount resumes from the last
record it saw, so no records are missed and none are replayed. `from:
"latest"` needs a server that supports it; older servers safely fall
back to a full replay.
([#4811](https://github.com/triggerdotdev/trigger.dev/pull/4811))

`useRealtimeStream` also gains a `lastEventId` option and returns the
`lastEventId` of the last part seen, so you can persist the cursor (for
example across a page reload) and resume exactly where you left off. An
`onParts` callback delivers each throttled batch of parts with their
event ids.

  ```tsx
const { parts, lastEventId } = useRealtimeStream<Frame>(runId, "frames",
{
    from: "latest", // skip history, start at the current tail
    maxParts: 1, // keep only the most recent frame
    lastEventId: savedCursor, // resume from a persisted cursor
    onParts: (batch) => save(batch.at(-1)?.id), // track the cursor
    accessToken,
  });
  ```
## @trigger.dev/python@4.5.14

### Patch Changes

- Updated dependencies:
  - `@trigger.dev/core@4.5.14`
  - `@trigger.dev/sdk@4.5.14`
  - `@trigger.dev/build@4.5.14`
## @trigger.dev/react-hooks@4.5.14

### Patch Changes

- Realtime stream subscriptions can now refresh an expired access token
and reconnect, via a new optional `refreshAccessToken` option on the
client configuration and the React hooks.
([#4811](https://github.com/triggerdotdev/trigger.dev/pull/4811))
- Subscribe to a realtime stream from its latest record instead of
replaying the whole history. Pass `from: "latest"` to
`useRealtimeStream`, `streams.read()`, or `fetchStream` to start at the
current tail (the latest record, then live updates) instead of replaying
(a live "last value" view), and `maxParts` to keep the accumulated
`parts` array bounded. A reconnect or remount resumes from the last
record it saw, so no records are missed and none are replayed. `from:
"latest"` needs a server that supports it; older servers safely fall
back to a full replay.
([#4811](https://github.com/triggerdotdev/trigger.dev/pull/4811))

`useRealtimeStream` also gains a `lastEventId` option and returns the
`lastEventId` of the last part seen, so you can persist the cursor (for
example across a page reload) and resume exactly where you left off. An
`onParts` callback delivers each throttled batch of parts with their
event ids.

  ```tsx
const { parts, lastEventId } = useRealtimeStream<Frame>(runId, "frames",
{
    from: "latest", // skip history, start at the current tail
    maxParts: 1, // keep only the most recent frame
    lastEventId: savedCursor, // resume from a persisted cursor
    onParts: (batch) => save(batch.at(-1)?.id), // track the cursor
    accessToken,
  });
  ```

- Added a `useSessionStream` React hook for reading a session's output
or input channel in realtime. It accumulates records with automatic
resume from the last record you received, and supports `from: "latest"`
(start at the current tail, only new records after you connect),
`maxRecords` (keep a bounded number of records in memory), a
`lastEventId` resume cursor, and an `onRecords` callback that delivers
each throttled batch of records with their event ids.
([#4811](https://github.com/triggerdotdev/trigger.dev/pull/4811))
- Updated dependencies:
  - `@trigger.dev/core@4.5.14`
## @trigger.dev/redis-worker@4.5.14

### Patch Changes

- Updated dependencies:
  - `@trigger.dev/core@4.5.14`
## @trigger.dev/rsc@4.5.14

### Patch Changes

- Updated dependencies:
  - `@trigger.dev/core@4.5.14`
## @trigger.dev/schema-to-json@4.5.14

### Patch Changes

- Updated dependencies:
  - `@trigger.dev/core@4.5.14`
## @trigger.dev/sdk@4.5.14

### Patch Changes

- Subscribe to a realtime stream from its latest record instead of
replaying the whole history. Pass `from: "latest"` to
`useRealtimeStream`, `streams.read()`, or `fetchStream` to start at the
current tail (the latest record, then live updates) instead of replaying
(a live "last value" view), and `maxParts` to keep the accumulated
`parts` array bounded. A reconnect or remount resumes from the last
record it saw, so no records are missed and none are replayed. `from:
"latest"` needs a server that supports it; older servers safely fall
back to a full replay.
([#4811](https://github.com/triggerdotdev/trigger.dev/pull/4811))

`useRealtimeStream` also gains a `lastEventId` option and returns the
`lastEventId` of the last part seen, so you can persist the cursor (for
example across a page reload) and resume exactly where you left off. An
`onParts` callback delivers each throttled batch of parts with their
event ids.

  ```tsx
const { parts, lastEventId } = useRealtimeStream<Frame>(runId, "frames",
{
    from: "latest", // skip history, start at the current tail
    maxParts: 1, // keep only the most recent frame
    lastEventId: savedCursor, // resume from a persisted cursor
    onParts: (batch) => save(batch.at(-1)?.id), // track the cursor
    accessToken,
  });
  ```

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

</details>

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
2026-08-28 21:39:08 +01:00

13 KiB
Raw Blame History

@trigger.dev/python

4.5.14

Patch Changes

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

4.5.13

Patch Changes

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

4.5.12

Patch Changes

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

4.5.11

Patch Changes

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

4.5.10

Patch Changes

  • Refresh package builds for TypeScript 7 compatibility while preserving existing runtime entry points. Projects using emitDecoratorMetadata() with TypeScript 7 can install the @typescript/typescript6 compatibility package alongside it; the package remains optional, so installing the Trigger.dev CLI does not install an additional compiler. (#4318)
  • Updated dependencies:
    • @trigger.dev/sdk@4.5.10
    • @trigger.dev/core@4.5.10
    • @trigger.dev/build@4.5.10

4.5.9

Patch Changes

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

4.5.8

Patch Changes

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

4.5.7

Patch Changes

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

4.5.6

Patch Changes

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

4.5.5

Patch Changes

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

4.5.4

Patch Changes

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

4.5.3

Patch Changes

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

4.5.2

Patch Changes

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

4.5.1

Patch Changes

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

4.5.0

Patch Changes

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

4.5.0-rc.7

Patch Changes

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

4.5.0-rc.6

Patch Changes

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

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

4.5.0-rc.4

Patch Changes

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

4.5.0-rc.3

Patch Changes

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

4.5.0-rc.2

Patch Changes

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

4.5.0-rc.1

Patch Changes

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

4.5.0-rc.0

Patch Changes

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

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