Remove references to v4

samejr · samejr · commit 8a4ae7cb54ef · 2025-07-22T15:31:20.000+01:00
diff --git a/docs/cli-preview-archive.mdx b/docs/cli-preview-archive.mdx
@@ -2,10 +2,8 @@
 title: "CLI preview archive command"
 sidebarTitle: "preview archive"
 description: "The `trigger.dev preview archive` command can be used to archive a preview branch."
-tag: "v4"
 ---
 
-import UpgradeToV4Note from "/snippets/upgrade-to-v4-note.mdx";
 import ProjectPathArg from "/snippets/cli-args-project-path.mdx";
 import CommonOptions from "/snippets/cli-options-common.mdx";
 import ProjectRefOption from "/snippets/cli-options-project-ref.mdx";
@@ -14,8 +12,6 @@ import ConfigFileOption from "/snippets/cli-options-config-file.mdx";
 import SkipUpdateCheckOption from "/snippets/cli-options-skip-update-check.mdx";
 import BranchOption from "/snippets/cli-options-branch.mdx";
 
-<UpgradeToV4Note />
-
 Run the command like this:
 
 <CodeGroup>
diff --git a/docs/cli-switch.mdx b/docs/cli-switch.mdx
@@ -2,10 +2,8 @@
 title: "CLI switch command"
 sidebarTitle: "switch"
 description: "The `trigger.dev switch` command can be used to switch between profiles."
-tag: "v4"
 ---
 
-import UpgradeToV4Note from "/snippets/upgrade-to-v4-note.mdx";
 import ProjectPathArg from "/snippets/cli-args-project-path.mdx";
 import CommonOptions from "/snippets/cli-options-common.mdx";
 import ProjectRefOption from "/snippets/cli-options-project-ref.mdx";
@@ -14,8 +12,6 @@ import ConfigFileOption from "/snippets/cli-options-config-file.mdx";
 import SkipUpdateCheckOption from "/snippets/cli-options-skip-update-check.mdx";
 import BranchOption from "/snippets/cli-options-branch.mdx";
 
-<UpgradeToV4Note />
-
 Run the command like this:
 
 <CodeGroup>
diff --git a/docs/config/extensions/playwright.mdx b/docs/config/extensions/playwright.mdx
@@ -2,13 +2,8 @@
 title: "Playwright"
 sidebarTitle: "playwright"
 description: "Use the playwright build extension to use Playwright with Trigger.dev"
-tag: "v4"
 ---
 
-import UpgradeToV4Note from "/snippets/upgrade-to-v4-note.mdx";
-
-<UpgradeToV4Note />
-
 If you are using [Playwright](https://playwright.dev/), you should use the Playwright build extension.
 
 - Automatically installs Playwright and required browser dependencies
diff --git a/docs/deployment/preview-branches.mdx b/docs/deployment/preview-branches.mdx
@@ -1,13 +1,8 @@
 ---
 title: "Preview branches"
 description: "Create isolated environments for each branch of your code, allowing you to test changes before merging to production. You can create preview branches manually or automatically from your git branches."
-tag: "v4"
 ---
 
-import UpgradeToV4Note from "/snippets/upgrade-to-v4-note.mdx";
-
-<UpgradeToV4Note />
-
 ## How to use preview branches
 
 The preview environment is special – you create branches from it. The branches you create live under the preview environment and have all the features you're used to from other environments (like staging or production). That means you can trigger runs, have schedules, test them, use Realtime, etc.
diff --git a/docs/guides/example-projects/human-in-the-loop-workflow.mdx b/docs/guides/example-projects/human-in-the-loop-workflow.mdx
@@ -2,11 +2,8 @@
 title: "Human-in-the-loop workflow with ReactFlow and Trigger.dev waitpoint tokens"
 sidebarTitle: "Human-in-the-loop workflow"
 description: "This example project creates audio summaries of newspaper articles using a human-in-the-loop workflow built with ReactFlow and Trigger.dev waitpoint tokens."
-tag: "v4"
 ---
 
-import UpgradeToV4Note from "/snippets/upgrade-to-v4-note.mdx";
-
 ## Overview
 
 This demo is a full stack example that uses the following:
@@ -77,9 +74,6 @@ await wait.completeToken<ReviewPayload>(
 );
 ```
 
-<UpgradeToV4Note />
-
-
 While the workflow in this example is static and does not allow changing the connections between nodes in the UI, it serves as a good baseline for understanding how to build completely custom workflow builders using Trigger.dev and ReactFlow.
 
 ## Learn more about Trigger.dev Realtime and waitpoint tokens
diff --git a/docs/guides/example-projects/mastra-agents-with-memory.mdx b/docs/guides/example-projects/mastra-agents-with-memory.mdx
@@ -2,13 +2,8 @@
 title: "Mastra agents with memory sharing + Trigger.dev task orchestration"
 sidebarTitle: "Mastra agents with memory"
 description: "Multi-agent workflow with persistent memory sharing using Mastra and Trigger.dev for clothing recommendations based on weather data."
-tag: "v4"
 ---
 
-import UpgradeToV4Note from "/snippets/upgrade-to-v4-note.mdx";
-
-<UpgradeToV4Note />
-
 ## Overview
 
 Enter a city and an activity, and get a clothing recommendation generated for you based on today's weather.
diff --git a/docs/guides/example-projects/meme-generator-human-in-the-loop.mdx b/docs/guides/example-projects/meme-generator-human-in-the-loop.mdx
@@ -2,13 +2,8 @@
 title: "Meme generator with human-in-the-loop approval"
 sidebarTitle: "AI meme generator"
 description: "This example project creates memes using OpenAI's DALL-E 3 with a human-in-the-loop approval workflow built using Trigger.dev waitpoint tokens."
-tag: "v4"
 ---
 
-import UpgradeToV4Note from "/snippets/upgrade-to-v4-note.mdx";
-
-<UpgradeToV4Note />
-
 ## Overview
 
 This demo is a full stack example that uses the following:
diff --git a/docs/guides/example-projects/openai-agents-sdk-typescript-playground.mdx b/docs/guides/example-projects/openai-agents-sdk-typescript-playground.mdx
@@ -2,7 +2,6 @@
 title: "OpenAI Agents SDK for Typescript + Trigger.dev playground"
 sidebarTitle: "OpenAI Agents SDK for Typescript playground"
 description: "Build production-ready AI agents with OpenAI Agents SDK for Typescript and Trigger.dev. Explore 7 examples covering streaming, multi-agent systems, and tool integration."
-tag: "v4"
 ---
 
 ## Overview
diff --git a/docs/guides/example-projects/vercel-ai-sdk-deep-research.mdx b/docs/guides/example-projects/vercel-ai-sdk-deep-research.mdx
@@ -2,15 +2,10 @@
 title: "Deep research agent using Vercel's AI SDK"
 sidebarTitle: "Deep research agent"
 description: "Deep research agent which generates comprehensive PDF reports using Vercel's AI SDK."
-tag: "v4"
 ---
 
 import RealtimeLearnMore from "/snippets/realtime-learn-more.mdx";
 
-import UpgradeToV4Note from "/snippets/upgrade-to-v4-note.mdx";
-
-<UpgradeToV4Note />
-
 <Info title="Acknowledgements">
   Acknowledgements: This example project is derived from the brilliant [deep research
   guide](https://aie-feb-25.vercel.app/docs/deep-research) by [Nico
diff --git a/docs/runs/priority.mdx b/docs/runs/priority.mdx
@@ -1,13 +1,8 @@
 ---
 title: "Priority"
 description: "Specify a priority when triggering a run."
-tag: "v4"
 ---
 
-import UpgradeToV4Note from "/snippets/upgrade-to-v4-note.mdx";
-
-<UpgradeToV4Note />
-
 You can set a priority when you trigger a run. This allows you to prioritize some of your runs over others, so they are started sooner. This is very useful when:
 
 - You have critical work that needs to start more quickly (and you have long queues).
diff --git a/docs/snippets/upgrade-to-v4-note.mdx b/docs/snippets/upgrade-to-v4-note.mdx
diff --git a/docs/wait-for-token.mdx b/docs/wait-for-token.mdx
@@ -1,17 +1,12 @@
 ---
 title: "Wait for token"
 description: "Wait until a token is completed."
-tag: "v4"
 ---
 
-import UpgradeToV4Note from "/snippets/upgrade-to-v4-note.mdx";
-
 Waitpoint tokens pause task runs until you complete the token. They're commonly used for approval workflows and other scenarios where you need to wait for external confirmation, such as human-in-the-loop processes.
 
 You can complete a token using the SDK or by making a POST request to the token's URL.
 
-<UpgradeToV4Note />
-
 ## Usage
 
 To get started using wait tokens, you need to first create a token using the `wait.createToken` function:
