Skip to content

v.docker.4.5.16

v.docker.4.5.16: chore: release v4.5.16 (#4856)
@github-actions github-actions tagged this 02 Sep 17:12 
## Summary
1 improvement, 2 bug fixes.

## Improvements
- The `trigger.dev deploy` and `trigger.dev dev` commands now warn (with
the suggested fix) when your code loads a package through
`createRequire()` that won't be available in the deployed image.
Previously it would fail at runtime in production to load the package.
Deploys also now show bundler warnings for your code instead of
discarding them.
([#4851](https://github.com/triggerdotdev/trigger.dev/pull/4851))

## Bug fixes
- Fixes an issue introduced in 4.5.11 that made deploy image builds of
projects with large dependency trees noticeably slower.
([#4878](https://github.com/triggerdotdev/trigger.dev/pull/4878))

## Server changes

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

- A durable guard improves reliability for runs waiting on
triggerAndWait or batchTriggerAndWait if there's a database error that
interrupts a child run finishing.
([#4849](https://github.com/triggerdotdev/trigger.dev/pull/4849))

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

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

### Patch Changes

- The `trigger.dev deploy` and `trigger.dev dev` commands now warn (with
the suggested fix) when your code loads a package through
`createRequire()` that won't be available in the deployed image.
Previously it would fail at runtime in production to load the package.
Deploys also now show bundler warnings for your code instead of
discarding them.
([#4851](https://github.com/triggerdotdev/trigger.dev/pull/4851))
- Updated dependencies:
  - `@trigger.dev/core@4.5.16`
## trigger.dev@4.5.16

### Patch Changes

- Fixes an issue introduced in 4.5.11 that made deploy image builds of
projects with large dependency trees noticeably slower.
([#4878](https://github.com/triggerdotdev/trigger.dev/pull/4878))
- The `trigger.dev deploy` and `trigger.dev dev` commands now warn (with
the suggested fix) when your code loads a package through
`createRequire()` that won't be available in the deployed image.
Previously it would fail at runtime in production to load the package.
Deploys also now show bundler warnings for your code instead of
discarding them.
([#4851](https://github.com/triggerdotdev/trigger.dev/pull/4851))
- Updated dependencies:
  - `@trigger.dev/build@4.5.16`
  - `@trigger.dev/core@4.5.16`
  - `@trigger.dev/schema-to-json@4.5.16`
## @trigger.dev/core@4.5.16

### Patch Changes

- The `trigger.dev deploy` and `trigger.dev dev` commands now warn (with
the suggested fix) when your code loads a package through
`createRequire()` that won't be available in the deployed image.
Previously it would fail at runtime in production to load the package.
Deploys also now show bundler warnings for your code instead of
discarding them.
([#4851](https://github.com/triggerdotdev/trigger.dev/pull/4851))
## @trigger.dev/python@4.5.16

### Patch Changes

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

### Patch Changes

- Updated dependencies:
  - `@trigger.dev/core@4.5.16`
## @trigger.dev/redis-worker@4.5.16

### Patch Changes

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

### Patch Changes

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

### Patch Changes

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

### Patch Changes

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

</details>

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