Updates @v4-beta to @latest

Author: samejr

docs/cli-preview-archive.mdx

@@ -17,15 +17,15 @@ Run the command like this:
 <CodeGroup>
 
 ```bash npm
-npx trigger.dev@v4-beta preview archive
+npx trigger.dev@latest preview archive
 ```
 
 ```bash pnpm
-pnpm dlx trigger.dev@v4-beta preview archive
+pnpm dlx trigger.dev@latest preview archive
 ```
 
 ```bash yarn
-yarn dlx trigger.dev@v4-beta preview archive
+yarn dlx trigger.dev@latest preview archive
 ```
 
 </CodeGroup>
@@ -35,7 +35,7 @@ It will archive the preview branch, automatically detecting the branch name from
 ## Arguments
 
 ```
-npx trigger.dev@v4-beta preview archive [path]
+npx trigger.dev@latest preview archive [path]
 ```
 
 <ProjectPathArg />

docs/cli-switch.mdx

@@ -17,15 +17,15 @@ Run the command like this:
 <CodeGroup>
 
 ```bash npm
-npx trigger.dev@v4-beta switch [profile]
+npx trigger.dev@latest switch [profile]
 ```
 
 ```bash pnpm
-pnpm dlx trigger.dev@v4-beta switch [profile]
+pnpm dlx trigger.dev@latest switch [profile]
 ```
 
 ```bash yarn
-yarn dlx trigger.dev@v4-beta switch [profile]
+yarn dlx trigger.dev@latest switch [profile]
 ```
 
 </CodeGroup>
@@ -35,7 +35,7 @@ It will switch to the specified profile. If no profile is specified, it will lis
 ## Arguments
 
 ```
-npx trigger.dev@v4-beta switch [profile]
+npx trigger.dev@latest switch [profile]
 ```
 
 <ParamField body="Profile" type="[profile]">

docs/deployment/preview-branches.mdx

@@ -96,7 +96,7 @@ jobs:
         run: npm install
 
       - name: Deploy preview branch
-        run: npx trigger.dev@v4-beta deploy --env preview
+        run: npx trigger.dev@latest deploy --env preview
         env:
           TRIGGER_ACCESS_TOKEN: ${{ secrets.TRIGGER_ACCESS_TOKEN }}
 ```
@@ -116,21 +116,21 @@ You can manually specify the branch using `--branch <branch-name>` in the deploy
 Creating and deploying a preview branch manually is easy:
 
 ```bash
-npx trigger.dev@v4-beta deploy --env preview
+npx trigger.dev@latest deploy --env preview
 ```
 
 This will create and deploy a preview branch, automatically detecting the git branch. If for some reason the auto-detection doesn't work it will let you know and tell you do this:
 
 ```bash
-npx trigger.dev@v4-beta deploy --env preview --branch your-branch-name
+npx trigger.dev@latest deploy --env preview --branch your-branch-name
 ```
 
 ### Archiving a preview branch
 
 You can manually archive a preview branch with the CLI:
 
 ```bash
-npx trigger.dev@v4-beta preview archive
+npx trigger.dev@latest preview archive
 ```
 
 Again we will try auto-detect the current branch. But you can specify the branch name with `--branch <branch-name>`.

docs/self-hosting/docker.mdx

@@ -102,7 +102,7 @@ docker compose logs -f webapp
 6. (optional) To initialize a new project, run the following command:
 
 ```bash
-npx trigger.dev@v4-beta init -p <project-ref> -a http://localhost:8030
+npx trigger.dev@latest init -p <project-ref> -a http://localhost:8030
 ```
 
 <Warning>
@@ -349,16 +349,12 @@ TRIGGER_IMAGE_TAG=v4.0.0-v4-beta.21
 
 This section highlights some of the CLI commands and options that are useful when self-hosting. Please check the [CLI reference](/cli-introduction) for more in-depth documentation.
 
-<Warning>
-While v4 is in beta, always use `@v4-beta` instead of `@latest`. For example: `npx trigger.dev@v4-beta dev`
-</Warning>
-
 ### Login
 
 To avoid being redirected to [Trigger.dev Cloud](https://cloud.trigger.dev) when using the CLI, you need to specify the URL of your self-hosted instance with the `--api-url` or `-a` flag. For example:
 
 ```bash
-npx trigger.dev@v4-beta login -a http://trigger.example.com
+npx trigger.dev@latest login -a http://trigger.example.com
 ```
 
 Once you've logged in, you shouldn't have to specify the URL again with other commands.
@@ -368,7 +364,7 @@ Once you've logged in, you shouldn't have to specify the URL again with other co
 You can specify a profile when logging in. This allows you to easily use the CLI with multiple instances of Trigger.dev. For example:
 
 ```bash
-npx trigger.dev@v4-beta login -a http://trigger.example.com \
+npx trigger.dev@latest login -a http://trigger.example.com \
     --profile self-hosted
 ```
 
@@ -377,37 +373,37 @@ Logging in with a new profile will also make it the new default profile.
 To use a specific profile, you can use the `--profile` flag with other commands:
 
 ```bash
-npx trigger.dev@v4-beta dev --profile self-hosted
+npx trigger.dev@latest dev --profile self-hosted
 ```
 
 To list all your profiles, use the `list-profiles` command:
 
 ```bash
-npx trigger.dev@v4-beta list-profiles
+npx trigger.dev@latest list-profiles
 ```
 
 To remove a profile, use the `logout` command:
 
 ```bash
-npx trigger.dev@v4-beta logout --profile self-hosted
+npx trigger.dev@latest logout --profile self-hosted
 ```
 
 To switch to a different profile, use the `switch` command:
 
 ```bash
 # To run interactively
-npx trigger.dev@v4-beta switch
+npx trigger.dev@latest switch
 
 # To switch to a specific profile
-npx trigger.dev@v4-beta switch self-hosted
+npx trigger.dev@latest switch self-hosted
 ```
 
 ### Whoami
 
 It can be useful to check you are logged into the correct instance. Running this will also show the API URL:
 
 ```bash
-npx trigger.dev@v4-beta whoami
+npx trigger.dev@latest whoami
 ```
 
 ## CI / GitHub Actions