You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat(webapp): gracefully shut down the v3 engine behind a flag
Adds DEPRECATE_V3_ENABLED (default off). When on, triggers that resolve to
v3 are rejected with a message pointing at the v4 migration guide, the
legacy dev websocket is closed, the v3 shared-queue consumer won't start,
and the v3 run-lifecycle background jobs (heartbeat timeout, TTL expiry,
retry, resume, delayed-run enqueue, scheduled fires) become no-ops so
abandoned v3 runs stop generating database load. Every gate also checks the
run or project is v3, so v4 is unaffected.
When the v3 engine is retired, triggering a v3 task and connecting the v3 dev CLI now fail with a clear message pointing to the v4 migration guide instead of failing opaquely. Enforcement is off by default, so self-hosted instances still running v3 are unaffected until they migrate.
exportconstV3_TRIGGER_DEPRECATION_MESSAGE=`Trigger.dev v3 is no longer supported. Please upgrade your project to v4 to keep triggering tasks: ${V3_MIGRATION_URL}`;
24
+
25
+
// Sent as a websocket close reason, which is capped at 123 bytes, so keep it short.
26
+
exportconstV3_DEV_DEPRECATION_MESSAGE=`Trigger.dev v3 is no longer supported. Upgrade to v4: ${V3_MIGRATION_URL}`;
27
+
28
+
/**
29
+
* Whether the v3 (engine V1) shutdown is being enforced. Guard every V1-only
30
+
* code path with `isV3Disabled() && <run/project is V1>` so v4 is untouched.
0 commit comments