chore: release v4.5.0-rc.8

.changeset/pre.json

@@ -29,9 +29,12 @@
     "cap-idempotency-key-length",
     "chat-agent-hardening",
     "chat-agent-on-boot-hook",
+    "chat-agent-preview-branch",
     "chat-agent-tools",
     "chat-agent",
     "chat-boot-cursor",
+    "chat-head-start-prepare-messages",
+    "chat-headstart-api-client",
     "chat-headstart-custom-backends",
     "chat-headstart-hydrate",
     "chat-headstart-reasoning",
@@ -40,6 +43,7 @@
     "chat-session-attributes",
     "chat-slim-wire-merge",
     "chat-start-session-action-typed-client-data",
+    "chat-start-session-api-client",
     "chat-system-prompt-caching",
     "chat-transport-recreate-missing-session",
     "cli-deploy-skip-rewrite-timestamp",
@@ -49,14 +53,18 @@
     "create-session-stop-continuation",
     "custom-agent-loop-fixes",
     "dequeue-latency-histogram",
+    "dev-branches",
     "duplicate-task-ids",
     "env-vars-tracing-forceflush-typecheck",
     "envvars-import-is-secret",
+    "errors-api-schemas",
+    "httpserver-skip-body-parsing",
     "large-trigger-payload-offload",
     "locals-key-dual-package-fix",
     "mcp-agent-chat-sessions",
     "mcp-list-runs-region",
     "mcp-trigger-task-no-default-wait",
+    "mint-token-command",
     "mock-chat-agent-test-harness",
     "mollifier-buffer-pipeline-list-entries",
     "mollifier-configurable-constants",
@@ -69,6 +77,7 @@
     "resource-catalog-runtime-registration",
     "retry-middleware-errors",
     "retry-sigsegv",
+    "runner-send-debug-logs-gate",
     "runs-list-region-filter",
     "s2-batch-transform-linger-fix",
     "sessions-primitive",

hosting/k8s/helm/Chart.yaml

@@ -2,8 +2,8 @@ apiVersion: v2
 name: trigger
 description: The official Trigger.dev Helm chart
 type: application
-version: 4.5.0-rc.7
-appVersion: v4.5.0-rc.7
+version: 4.5.0-rc.8
+appVersion: v4.5.0-rc.8
 home: https://trigger.dev
 sources:
   - https://github.com/triggerdotdev/trigger.dev

packages/build/CHANGELOG.md

@@ -1,5 +1,12 @@
 # @trigger.dev/build
 
+## 4.5.0-rc.8
+
+### Patch Changes
+
+- Updated dependencies:
+  - `@trigger.dev/core@4.5.0-rc.8`
+
 ## 4.5.0-rc.7
 
 ### Patch Changes
@@ -56,7 +63,10 @@
 - Add Agent Skills for `chat.agent`. Drop a folder with a `SKILL.md` and any helper scripts/references next to your task code, register it with `skills.define({ id, path })`, and the CLI bundles it into the deploy image automatically — no `trigger.config.ts` changes. The agent gets a one-line summary in its system prompt and discovers full instructions on demand via `loadSkill`, with `bash` and `readFile` tools scoped per-skill (path-traversal guards, output caps, abort-signal propagation). ([#3543](https://github.com/triggerdotdev/trigger.dev/pull/3543))
 
   ```ts
-  const pdfSkill = skills.define({ id: "pdf-extract", path: "./skills/pdf-extract" });
+  const pdfSkill = skills.define({
+    id: "pdf-extract",
+    path: "./skills/pdf-extract",
+  });
 
   chat.skills.set([await pdfSkill.local()]);
   ```
@@ -166,7 +176,6 @@
 - The `prismaExtension` has been completely redesigned to support multiple Prisma versions and deployment strategies. This update introduces **three distinct modes** to handle the evolving Prisma ecosystem, from legacy setups to the upcoming Prisma 7. ([#2689](https://github.com/triggerdotdev/trigger.dev/pull/2689))
 
   **Highlights:**
-
   - 🎯 Three modes: Legacy, Engine-Only, and Modern
   - 🎉 **NEW:** Support for `prisma.config.ts` files (Legacy Mode)
   - 🔍 **NEW:** Enhanced version detection with filesystem fallback
@@ -215,7 +224,6 @@
   **Use when:** You're using Prisma 6.x or earlier with the `prisma-client-js` provider.
 
   **Features:**
-
   - Automatic `prisma generate` during deployment
   - Supports single-file schemas (`prisma/schema.prisma`)
   - Supports multi-file schemas (Prisma 6.7+, directory-based schemas)
@@ -264,7 +272,6 @@
   ```
 
   **Tested Versions:**
-
   - Prisma 6.14.0 ✅
   - Prisma 6.7.0+ (multi-file schema support) ✅
   - Prisma 5.x ✅
@@ -276,7 +283,6 @@
   **Use when:** You have a custom Prisma client output path and want to manage `prisma generate` yourself.
 
   **Features:**
-
   - Only installs Prisma engine binaries (no client generation)
   - Automatic version detection from `@prisma/client`
   - Manual override of version and binary target
@@ -316,7 +322,6 @@
   ```
 
   **Important Notes:**
-
   - You **must** run `prisma generate` yourself (typically in a prebuild script)
   - Your schema **must** include the correct `binaryTargets` for deployment to the trigger.dev cloud. The binary target is `debian-openssl-3.0.x`.
   - The extension sets `PRISMA_QUERY_ENGINE_LIBRARY` and `PRISMA_QUERY_ENGINE_SCHEMA_ENGINE` environment variables to the correct paths for the binary targets.
@@ -334,7 +339,6 @@
   ```
 
   **Tested Versions:**
-
   - Prisma 6.19.0 ✅
   - Prisma 6.16.0+ ✅
 
@@ -345,7 +349,6 @@
   **Use when:** You're using Prisma 6.16+ with the new `prisma-client` provider (with `engineType = "client"`) or preparing for Prisma 7.
 
   **Features:**
-
   - Designed for the new Prisma architecture
   - Zero configuration required
   - Automatically marks `@prisma/client` as external
@@ -409,14 +412,12 @@
   ```
 
   **Important Notes:**
-
   - You **must** run `prisma generate` yourself
   - Requires Prisma 6.16.0+ or Prisma 7 beta
   - The new `prisma-client` provider generates plain TypeScript (no Rust binaries)
   - Requires database adapters (e.g., `@prisma/adapter-pg` for PostgreSQL)
 
   **Tested Versions:**
-
   - Prisma 6.16.0 with `engineType = "client"` ✅
   - Prisma 6.20.0-integration-next.8 (Prisma 7 beta) ✅
 
@@ -457,7 +458,6 @@
   ### Preparing for Prisma 7
 
   If you want to adopt the new Prisma architecture, use **Modern Mode**:
-
   1. Update your schema to use `prisma-client` provider
   2. Add database adapters to your dependencies
   3. Configure the extension:
@@ -489,7 +489,6 @@
   **Use when:** You want to use Prisma's new config file format (Prisma 6+) to centralize your Prisma configuration.
 
   **Benefits:**
-
   - Single source of truth for Prisma configuration
   - Automatic extraction of schema location and migrations path
   - Type-safe configuration with TypeScript
@@ -527,7 +526,6 @@
   ```
 
   **What gets extracted:**
-
   - `schema` - The schema file or directory path
   - `migrations.path` - The migrations directory path (if specified)
 

packages/build/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@trigger.dev/build",
-  "version": "4.5.0-rc.7",
+  "version": "4.5.0-rc.8",
   "description": "trigger.dev build extensions",
   "license": "MIT",
   "publishConfig": {
@@ -78,7 +78,7 @@
   },
   "dependencies": {
     "@prisma/config": "^6.10.0",
-    "@trigger.dev/core": "workspace:4.5.0-rc.7",
+    "@trigger.dev/core": "workspace:4.5.0-rc.8",
     "mlly": "^1.7.1",
     "pkg-types": "^1.1.3",
     "resolve": "^1.22.8",