chore: remove end-of-life v3 execution components

.changeset/config.json

@@ -14,9 +14,6 @@
  "updateInternalDependencies": "patch",
  "ignore": [
  "webapp",
- "coordinator",
- "docker-provider",
- "kubernetes-provider",
  "supervisor"
  ],
  "___experimentalUnsafeOptions_WILL_CHANGE_IN_PATCH": {

.changeset/wild-v3-provider-helpers.md

@@ -0,0 +1,5 @@
+---
+"@trigger.dev/core": patch
+---
+
+Removed internal helpers that were only used by the end-of-life v3 self-hosted compute providers.

.claude/rules/server-apps.md

@@ -5,7 +5,7 @@ paths:
 
 # Server App Changes
 
-When modifying server apps (webapp, supervisor, coordinator, etc.) with **no package changes**, add a `.server-changes/` file instead of a changeset:
+When modifying server apps (webapp, supervisor, etc.) with **no package changes**, add a `.server-changes/` file instead of a changeset:
 
 ```bash
 cat > .server-changes/descriptive-name.md << 'EOF'
@@ -18,6 +18,6 @@ Brief description of what changed and why.
 EOF
 ```
 
-- **area**: `webapp` | `supervisor` | `coordinator` | `kubernetes-provider` | `docker-provider`
+- **area**: `webapp` | `supervisor`
 - **type**: `feature` | `fix` | `improvement` | `breaking`
 - If the PR also touches `packages/`, just the changeset is sufficient (no `.server-changes/` needed).

.cursorignore

@@ -1,7 +1,4 @@
-apps/docker-provider/
-apps/kubernetes-provider/
 apps/proxy/
-apps/coordinator/
 packages/rsc/
 .changeset
 .zed

.github/workflows/publish.yml

@@ -30,7 +30,6 @@ on:
  - ".github/workflows/unit-tests.yml"
  - ".github/workflows/e2e.yml"
  - ".github/workflows/publish-webapp.yml"
- - ".github/workflows/publish-worker.yml"
  - "packages/**"
  - "!packages/**/*.md"
  - "!packages/**/*.eslintrc"
@@ -80,19 +79,6 @@ jobs:
  # to its own namespace; set the IMAGE_REGISTRY repository variable to override.
  image_registry: ${{ vars.IMAGE_REGISTRY || format('ghcr.io/{0}', github.repository_owner) }}
 
- publish-worker:
- needs: [typecheck]
- permissions:
- contents: read
- packages: write
- uses: ./.github/workflows/publish-worker.yml
- secrets:
- DOCKERHUB_USERNAME: ${{ secrets.DOCKERHUB_USERNAME }}
- DOCKERHUB_TOKEN: ${{ secrets.DOCKERHUB_TOKEN }}
- with:
- image_tag: ${{ inputs.image_tag }}
- image_registry: ${{ vars.IMAGE_REGISTRY || format('ghcr.io/{0}', github.repository_owner) }}
-
  publish-worker-v4:
  needs: [typecheck]
  permissions:

.server-changes/README.md

@@ -1,10 +1,10 @@
 # Server Changes
 
-This directory tracks changes to server-only components (webapp, supervisor, coordinator, etc.) that are not captured by changesets. Changesets only track published npm packages — server changes would otherwise go undocumented.
+This directory tracks changes to server-only components (webapp, supervisor, etc.) that are not captured by changesets. Changesets only track published npm packages — server changes would otherwise go undocumented.
 
 ## When to add a file
 
-**Server-only PRs**: If your PR only changes `apps/webapp/`, `apps/supervisor/`, `apps/coordinator/`, or other server components (and does NOT change anything in `packages/`), add a `.server-changes/` file.
+**Server-only PRs**: If your PR only changes `apps/webapp/`, `apps/supervisor/`, or other server components (and does NOT change anything in `packages/`), add a `.server-changes/` file.
 
 **Mixed PRs** (both packages and server): Just add a changeset as usual. No `.server-changes/` file needed — the changeset covers it.
 
@@ -31,7 +31,7 @@ Speed up batch queue processing by removing stalls and fixing retry race
 
 ### Fields
 
-- **area** (required): `webapp` | `supervisor` | `coordinator` | `kubernetes-provider` | `docker-provider`
+- **area** (required): `webapp` | `supervisor`
 - **type** (required): `feature` | `fix` | `improvement` | `breaking`
 
 ### Description

CHANGESETS.md

@@ -21,7 +21,7 @@ Speed up batch queue processing by removing stalls and fixing retry race
 EOF
 ```
 
-- `area`: `webapp` | `supervisor` | `coordinator` | `kubernetes-provider` | `docker-provider`
+- `area`: `webapp` | `supervisor`
 - `type`: `feature` | `fix` | `improvement` | `breaking`
 
 For **mixed PRs** (both packages and server): just add a changeset. No `.server-changes/` file needed.

CONTRIBUTING.md

@@ -265,7 +265,7 @@ Most of the time the changes you'll make are likely to be categorized as patch r
 
 ## Adding server changes
 
-Changesets only track published npm packages. If your PR only changes server components (`apps/webapp/`, `apps/supervisor/`, `apps/coordinator/`, etc.) with no package changes, add a `.server-changes/` file so the change appears in release notes.
+Changesets only track published npm packages. If your PR only changes server components (`apps/webapp/`, `apps/supervisor/`, etc.) with no package changes, add a `.server-changes/` file so the change appears in release notes.
 
 Create a markdown file with a descriptive name:
 
@@ -281,7 +281,7 @@ EOF
 ```
 
 **Fields:**
-- `area` (required): `webapp` | `supervisor` | `coordinator` | `kubernetes-provider` | `docker-provider`
+- `area` (required): `webapp` | `supervisor`
 - `type` (required): `feature` | `fix` | `improvement` | `breaking`
 
 The body text (below the frontmatter) is a one-line description of the change. Keep it concise — it will appear in release notes.