Skip to content

Commit dab496a

Browse files
committed
docs(ai-chat): add 4.5.0-rc.1 changelog entry
Two bug fixes shipping in the patch RC: - Agent Skills folders silently missing in trigger dev when task files read process.env at module top level - COULD_NOT_FIND_EXECUTOR on dynamically-imported task definitions
1 parent 58a8f2e commit dab496a

1 file changed

Lines changed: 20 additions & 0 deletions

File tree

docs/ai-chat/changelog.mdx

Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -4,6 +4,26 @@ sidebarTitle: "Changelog"
44
description: "Pre-release updates for AI chat agents."
55
---
66

7+
<Update label="May 21, 2026" description="4.5.0-rc.1" tags={["SDK", "Bug fix"]}>
8+
9+
## v4.5.0-rc.1 — two bug fixes
10+
11+
Patch release on top of `4.5.0-rc.0`. Upgrade with:
12+
13+
```sh
14+
npx trigger.dev@4.5.0-rc.1 update # npm
15+
pnpm dlx trigger.dev@4.5.0-rc.1 update # pnpm
16+
yarn dlx trigger.dev@4.5.0-rc.1 update # yarn
17+
bunx trigger.dev@4.5.0-rc.1 update # bun
18+
```
19+
20+
### Fixes
21+
22+
- **Agent Skills silently missing in `trigger dev`** for projects whose task files read `process.env` at module top level (e.g. a third-party SDK client initialized at import). [Skill folders](/ai-chat/patterns/skills) now bundle into `.trigger/skills/` reliably regardless of which env vars are set when the CLI launches. ([#3690](https://github.com/triggerdotdev/trigger.dev/pull/3690))
23+
- **`COULD_NOT_FIND_EXECUTOR`** when a task's definition is loaded via `await import(...)` from inside another task's `run()` — common when lazy-loading sub-agent tasks. Runtime workers now register such tasks with a sentinel file context, and the catalog logs a one-time warning per task id. ([#3688](https://github.com/triggerdotdev/trigger.dev/pull/3688))
24+
25+
</Update>
26+
727
<Update label="May 21, 2026" description="4.5.0-rc.0" tags={["SDK", "Release"]}>
828

929
## v4.5.0-rc.0 — AI Agents graduate from chat-prerelease

0 commit comments

Comments
 (0)