Got rid of some more @v4-beta mentions

Author: matt-aitken

docs/manual-setup.mdx

@@ -17,10 +17,10 @@ Before setting up your project, you need to authenticate the CLI with Trigger.de
 
 ```bash
 # Login to Trigger.dev
-npx trigger.dev@v4-beta login
+npx trigger.dev@latest login
 
 # Or with a specific API URL (for self-hosted instances)
-npx trigger.dev@v4-beta login --api-url https://your-trigger-instance.com
+npx trigger.dev@latest login --api-url https://your-trigger-instance.com
 ```
 
 This will open your browser to authenticate. Once authenticated, you'll need to select or create a project in the Trigger.dev dashboard to get your project reference (e.g., `proj_abc123`).
@@ -32,23 +32,23 @@ Install the required packages based on your package manager:
 <CodeGroup>
 
 ```bash npm
-npm add @trigger.dev/sdk@v4-beta
-npm add --save-dev @trigger.dev/build@v4-beta
+npm add @trigger.dev/sdk@latest
+npm add --save-dev @trigger.dev/build@latest
 ```
 
 ```bash pnpm
-pnpm add @trigger.dev/sdk@v4-beta
-pnpm add -D @trigger.dev/build@v4-beta
+pnpm add @trigger.dev/sdk@latest
+pnpm add -D @trigger.dev/build@latest
 ```
 
 ```bash yarn
-yarn add @trigger.dev/sdk@v4-beta
-yarn add -D @trigger.dev/build@v4-beta
+yarn add @trigger.dev/sdk@latest
+yarn add -D @trigger.dev/build@latest
 ```
 
 ```bash bun
-bun add @trigger.dev/sdk@v4-beta
-bun add -D @trigger.dev/build@v4-beta
+bun add @trigger.dev/sdk@latest
+bun add -D @trigger.dev/build@latest
 ```
 
 </CodeGroup>
@@ -82,13 +82,13 @@ You can run the Trigger.dev CLI in two ways:
 
 ```bash
 # npm
-npx trigger.dev@v4-beta dev
+npx trigger.dev@latest dev
 
 # pnpm
-pnpm dlx trigger.dev@v4-beta dev
+pnpm dlx trigger.dev@latest dev
 
 # yarn
-yarn dlx trigger.dev@v4-beta dev
+yarn dlx trigger.dev@latest dev
 ```
 
 ### Option 2: Add as dev dependency
@@ -98,7 +98,7 @@ Add the CLI to your `package.json`:
 ```json
 {
   "devDependencies": {
-    "trigger.dev": "4.0.0-v4-beta.26"
+    "trigger.dev": "^4.0.0"
   }
 }
 ```
@@ -120,11 +120,11 @@ Make sure to pin the version of the CLI to the same version as the SDK that you
 
 ```json
 "devDependencies": {
-  "trigger.dev": "4.0.0-v4-beta.26",
-  "@trigger.dev/build": "4.0.0-v4-beta.26"
+  "trigger.dev": "^4.0.0",
+  "@trigger.dev/build": "^4.0.0"
 },
 "dependencies": {
-  "@trigger.dev/sdk": "4.0.0-v4-beta.26"
+  "@trigger.dev/sdk": "^4.0.0"
 }
 ```
 
@@ -239,16 +239,16 @@ If you're building a React frontend application and want to display task status
 
 ```bash
 # npm
-npm install @trigger.dev/react-hooks@v4-beta
+npm install @trigger.dev/react-hooks@latest
 
 # pnpm
-pnpm add @trigger.dev/react-hooks@v4-beta
+pnpm add @trigger.dev/react-hooks@latest
 
 # yarn
-yarn add @trigger.dev/react-hooks@v4-beta
+yarn add @trigger.dev/react-hooks@latest
 
 # bun
-bun add @trigger.dev/react-hooks@v4-beta
+bun add @trigger.dev/react-hooks@latest
 ```
 
 ### Basic usage
@@ -396,10 +396,10 @@ packages:
   "name": "@repo/tasks",
   "version": "0.0.0",
   "dependencies": {
-    "@trigger.dev/sdk": "4.0.0-v4-beta.26"
+    "@trigger.dev/sdk": "^4.0.0"
   },
   "devDependencies": {
-    "@trigger.dev/build": "4.0.0-v4-beta.26"
+    "@trigger.dev/build": "^4.0.0"
   },
   "exports": {
     ".": "./src/trigger/index.ts",
@@ -509,7 +509,7 @@ Run the development server for the tasks package:
 ```bash
 # From the root of your monorepo
 cd packages/tasks
-npx trigger.dev@v4-beta dev
+npx trigger.dev@latest dev
 
 # Or using turbo (if you add dev:trigger script to tasks package.json)
 turbo run dev:trigger --filter=@repo/tasks
@@ -527,13 +527,13 @@ This approach installs Trigger.dev directly in individual apps that need backgro
 {
   "name": "web",
   "dependencies": {
-    "@trigger.dev/sdk": "4.0.0-v4-beta.26",
+    "@trigger.dev/sdk": "^4.0.0",
     "next": "^15.2.1",
     "react": "^19.0.0",
     "react-dom": "^19.0.0"
   },
   "devDependencies": {
-    "@trigger.dev/build": "4.0.0-v4-beta.26"
+    "@trigger.dev/build": "^4.0.0"
   }
 }
 ```
@@ -612,7 +612,7 @@ export async function triggerHelloWorld(name: string) {
 ```bash
 # From the app directory
 cd apps/web
-npx trigger.dev@v4-beta dev
+npx trigger.dev@latest dev
 
 # Or from the root using turbo
 turbo run dev:trigger --filter=web

docs/self-hosting/docker.mdx

@@ -14,6 +14,7 @@ Should the burden ever get too much, we'd be happy to see you on [Trigger.dev cl
 ## What's new?
 
 Goodbye v3, hello v4! We made quite a few changes:
+
 - **Much simpler setup.** The provider and coordinator are now combined into a single supervisor. No more startup scripts, just `docker compose up`.
 - **Automatic container cleanup.** The supervisor will automatically clean up containers that are no longer needed.
 - **Support for multiple worker machines.** This is a big one, and we're very excited about it! You can now scale your workers horizontally as needed.
@@ -105,13 +106,9 @@ docker compose logs -f webapp
 npx trigger.dev@latest init -p <project-ref> -a http://localhost:8030
 ```
 
-<Warning>
-The commands displayed in the webapp are incorrect while v4 is in beta. You should always use the `v4-beta` tag and not `latest`.
-</Warning>
-
-{/* 7. Bonus: Add traefik as a reverse proxy
+{/\* 7. Bonus: Add traefik as a reverse proxy
 
-```bash
+````bash
 docker compose -f docker-compose.yml -f ../docker-compose.traefik.yml up -d
 ``` */}
 
@@ -122,7 +119,7 @@ docker compose -f docker-compose.yml -f ../docker-compose.traefik.yml up -d
 ```bash
 git clone --depth=1 https://github.com/triggerdotdev/trigger.dev
 cd trigger.dev/hosting/docker
-```
+````
 
 2. Create a `.env` file
 
@@ -156,9 +153,9 @@ If you want to run the webapp and worker on the same machine, just replace the `
 docker compose -f webapp/docker-compose.yml -f worker/docker-compose.yml up -d
 ```
 
-{/* And optionally add traefik as a reverse proxy:
+{/\* And optionally add traefik as a reverse proxy:
 
-```bash
+````bash
 # Run this from the /hosting/docker directory
 docker compose -f webapp/docker-compose.yml -f worker/docker-compose.yml -f docker-compose.traefik.yml up -d
 ``` */}
@@ -188,7 +185,7 @@ Or, if using a file:
 TRIGGER_WORKER_TOKEN=file:///home/node/shared/worker_token
 
 ==========================
-```
+````
 
 You can then uncomment and set the `TRIGGER_WORKER_TOKEN` environment variable in your `.env` file.
 
@@ -245,7 +242,7 @@ You should change these before deploying to production, especially the password.
 ### Setup
 
 <Note>
-The `packets` bucket is created by default. In case this doesn't work, you can create it manually.
+  The `packets` bucket is created by default. In case this doesn't work, you can create it manually.
 </Note>
 
 1. Login to the dashboard: `http://localhost:9001`
@@ -323,13 +320,14 @@ This will apply to all auth methods including magic link and GitHub OAuth.
 ## Version locking
 
 There are several reasons to lock the version of your Docker images:
+
 - **Backwards compatibility.** We try our best to maintain compatibility with older CLI versions, but it's not always possible. If you don't want to update your CLI, you can lock your Docker images to that specific version.
 - **Ensuring full feature support.** Sometimes, new CLI releases will also require new or updated platform features. Running unlocked images can make any issues difficult to debug. Using a specific tag can help here as well.
 
-By default, the images will point at the latest versioned release via the `v4-beta` tag. You can override this by specifying a different tag in your `.env` file. For example:
+By default, the images will point at the latest versioned release via the `latest` tag. You can override this by specifying a different tag in your `.env` file. For example:
 
 ```bash
-TRIGGER_IMAGE_TAG=v4.0.0-v4-beta.21
+TRIGGER_IMAGE_TAG=v4.0.0
 ```
 
 ## Troubleshooting
@@ -408,7 +406,7 @@ npx trigger.dev@latest whoami
 
 ## CI / GitHub Actions
 
-When running the CLI in a CI environment, your login profiles won't be available. Instead, you can use the `TRIGGER_API_URL` and `TRIGGER_ACCESS_TOKEN` environment 
+When running the CLI in a CI environment, your login profiles won't be available. Instead, you can use the `TRIGGER_API_URL` and `TRIGGER_ACCESS_TOKEN` environment
 variables to point at your self-hosted instance and authenticate.
 
 For more detailed instructions, see the [GitHub Actions guide](/github-actions).