Skip to content

Commit dac2bb7

Browse files
committed
add warning at the top of the migrating to v4 page
1 parent a0737f5 commit dac2bb7

File tree

1 file changed

+14
-0
lines changed

1 file changed

+14
-0
lines changed

docs/migrating-from-v3.mdx

Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -6,6 +6,20 @@ description: "What's new in v4, how to migrate, and breaking changes."
66
import NodeVersions from "/snippets/node-versions.mdx";
77
import MigrateV4UsingAi from "/snippets/migrate-v4-using-ai.mdx";
88

9+
<Warning>
10+
**Action required: Trigger.dev v3 deprecation**
11+
12+
We're retiring Trigger.dev v3. **New v3 deploys will stop working from 1 April 2026.** Trigger.dev v4 is stable, fully supported, and recommended for all users.
13+
14+
**Key dates:**
15+
16+
- **1 April 2026** — New v3 deploys will no longer work. Existing v3 runs will continue to execute.
17+
- **1 July 2026** — v3 will be fully shut down. All v3 runs will stop executing.
18+
19+
**What you need to do:** Migrate to v4 before April to avoid disruption to your task executions. The migration takes about 2 minutes — follow the steps on this page below. If you have questions or need help, [contact us](https://trigger.dev/contact) or reach out in our [Discord](https://trigger.dev/discord).
20+
21+
</Warning>
22+
923
## What's new in v4?
1024

1125
| Feature | Description |

0 commit comments

Comments
 (0)