WIP docs update beta -> latest

Author: ericallam

docs/cli-init-commands.mdx

@@ -9,15 +9,15 @@ Run the command like this:
 <CodeGroup>
 
 ```bash npm
-npx trigger.dev@beta init
+npx trigger.dev@latest init
 ```
 
 ```bash pnpm
-pnpm dlx trigger.dev@beta init
+pnpm dlx trigger.dev@latest init
 ```
 
 ```bash yarn
-yarn dlx trigger.dev@beta init
+yarn dlx trigger.dev@latest init
 ```
 
 </CodeGroup>
@@ -53,7 +53,8 @@ yarn dlx trigger.dev@beta init
 </ParamField>
 
 <ParamField body="Log level" type="--log-level | -l">
-  The CLI log level to use. Options are `debug`, `info`, `log`, `warn`, `error`, and `none`. This does not affect the log level of your trigger.dev tasks. Defaults to "log".
+  The CLI log level to use. Options are `debug`, `info`, `log`, `warn`, `error`, and `none`. This
+  does not affect the log level of your trigger.dev tasks. Defaults to "log".
 </ParamField>
 
 <ParamField body="Skip telemetry" type="--skip-telemetry">
@@ -64,4 +65,4 @@ yarn dlx trigger.dev@beta init
 
 <ParamField body="Help" type="--help | -h">
   Shows the help information for the command.
-</ParamField>
+</ParamField>

docs/cli-list-profiles-commands.mdx

@@ -9,32 +9,32 @@ Run the command like this:
 <CodeGroup>
 
 ```bash npm
-npx trigger.dev@beta list-profiles
+npx trigger.dev@latest list-profiles
 ```
 
 ```bash pnpm
-pnpm dlx trigger.dev@beta list-profiles
+pnpm dlx trigger.dev@latest list-profiles
 ```
 
 ```bash yarn
-yarn dlx trigger.dev@beta list-profiles
+yarn dlx trigger.dev@latest list-profiles
 ```
 
 </CodeGroup>
 
 ## Options
 
 <ParamField body="Log level" type="--log-level | -l">
-  The CLI log level to use. Options are `debug`, `info`, `log`, `warn`, `error`, and `none`. This does not affect the log level of your trigger.dev tasks. Defaults to `log`.
+  The CLI log level to use. Options are `debug`, `info`, `log`, `warn`, `error`, and `none`. This
+  does not affect the log level of your trigger.dev tasks. Defaults to `log`.
 </ParamField>
 
 <ParamField body="Skip telemetry" type="--skip-telemetry">
   Opt-out of sending telemetry data.
 </ParamField>
 
-
 ## Standard options
 
 <ParamField body="Help" type="--help | -h">
   Shows the help information for the command.
-</ParamField>
+</ParamField>

docs/cli-login-commands.mdx

@@ -9,15 +9,15 @@ Run the command like this:
 <CodeGroup>
 
 ```bash npm
-npx trigger.dev@beta login
+npx trigger.dev@latest login
 ```
 
 ```bash pnpm
-pnpm dlx trigger.dev@beta login
+pnpm dlx trigger.dev@latest login
 ```
 
 ```bash yarn
-yarn dlx trigger.dev@beta login
+yarn dlx trigger.dev@latest login
 ```
 
 </CodeGroup>
@@ -33,7 +33,8 @@ yarn dlx trigger.dev@beta login
 </ParamField>
 
 <ParamField body="Log level" type="-l | --log-level">
-  Sets the CLI log level. Available options are `debug`, `info`, `log`, `warn`, `error`, and `none`. This setting doesn't affect the log level of your trigger.dev tasks. The default is `log`.
+  Sets the CLI log level. Available options are `debug`, `info`, `log`, `warn`, `error`, and `none`.
+  This setting doesn't affect the log level of your trigger.dev tasks. The default is `log`.
 </ParamField>
 
 <ParamField body="Skip telemetry" type="--skip-telemetry">
@@ -48,4 +49,4 @@ yarn dlx trigger.dev@beta login
 
 <ParamField body="Help" type="--help | -h">
   Shows the help information for the command.
-</ParamField>
+</ParamField>

docs/cli-logout-commands.mdx

@@ -9,15 +9,15 @@ Run the command like this:
 <CodeGroup>
 
 ```bash npm
-npx trigger.dev@beta logout
+npx trigger.dev@latest logout
 ```
 
 ```bash pnpm
-pnpm dlx trigger.dev@beta logout
+pnpm dlx trigger.dev@latest logout
 ```
 
 ```bash yarn
-yarn dlx trigger.dev@beta logout
+yarn dlx trigger.dev@latest logout
 ```
 
 </CodeGroup>
@@ -33,16 +33,16 @@ yarn dlx trigger.dev@beta logout
 </ParamField>
 
 <ParamField body="Log level" type="--log-level | -l">
-  The CLI log level to use. Options are `debug`, `info`, `log`, `warn`, `error`, and `none`. This does not affect the log level of your trigger.dev tasks. Defaults to `log`.
+  The CLI log level to use. Options are `debug`, `info`, `log`, `warn`, `error`, and `none`. This
+  does not affect the log level of your trigger.dev tasks. Defaults to `log`.
 </ParamField>
 
 <ParamField body="Skip telemetry" type="--skip-telemetry">
   Opt-out of sending telemetry data.
 </ParamField>
 
-
 ## Standard options
 
 <ParamField body="Help" type="--help | -h">
   Shows the help information for the command.
-</ParamField>
+</ParamField>

docs/cli-update-commands.mdx

@@ -9,32 +9,32 @@ Run the command like this:
 <CodeGroup>
 
 ```bash npm
-npx trigger.dev@beta update
+npx trigger.dev@latest update
 ```
 
 ```bash pnpm
-pnpm dlx trigger.dev@beta update
+pnpm dlx trigger.dev@latest update
 ```
 
 ```bash yarn
-yarn dlx trigger.dev@beta update
+yarn dlx trigger.dev@latest update
 ```
 
 </CodeGroup>
 
 ## Options
 
 <ParamField body="Log level" type="--log-level | -l">
-  The CLI log level to use. Options are `debug`, `info`, `log`, `warn`, `error`, and `none`. This does not affect the log level of your trigger.dev tasks. Defaults to `log`.
+  The CLI log level to use. Options are `debug`, `info`, `log`, `warn`, `error`, and `none`. This
+  does not affect the log level of your trigger.dev tasks. Defaults to `log`.
 </ParamField>
 
 <ParamField body="Skip telemetry" type="--skip-telemetry">
   Opt-out of sending telemetry data.
 </ParamField>
 
-
 ## Standard options
 
 <ParamField body="Help" type="--help | -h">
   Shows the help information for the command.
-</ParamField>
+</ParamField>

docs/cli-whoami-commands.mdx

@@ -9,15 +9,15 @@ Run the command like this:
 <CodeGroup>
 
 ```bash npm
-npx trigger.dev@beta whoami
+npx trigger.dev@latest whoami
 ```
 
 ```bash pnpm
-pnpm dlx trigger.dev@beta whoami
+pnpm dlx trigger.dev@latest whoami
 ```
 
 ```bash yarn
-yarn dlx trigger.dev@beta whoami
+yarn dlx trigger.dev@latest whoami
 ```
 
 </CodeGroup>
@@ -33,16 +33,16 @@ yarn dlx trigger.dev@beta whoami
 </ParamField>
 
 <ParamField body="Log level" type="--log-level | -l">
-  The CLI log level to use. Options are `debug`, `info`, `log`, `warn`, `error`, and `none`. This does not affect the log level of your trigger.dev tasks. Defaults to `log`.
+  The CLI log level to use. Options are `debug`, `info`, `log`, `warn`, `error`, and `none`. This
+  does not affect the log level of your trigger.dev tasks. Defaults to `log`.
 </ParamField>
 
 <ParamField body="Skip telemetry" type="--skip-telemetry">
   Opt-out of sending telemetry data.
 </ParamField>
 
-
 ## Standard options
 
 <ParamField body="Help" type="--help | -h">
   Shows the help information for the command.
-</ParamField>
+</ParamField>

docs/trigger-config.mdx renamed to docs/config/config-file.mdx

@@ -4,7 +4,7 @@ sidebarTitle: "trigger.config file"
 description: "This file is used to configure your project and how it's bundled."
 ---
 
-import BundlePackages from '/snippets/bundle-packages.mdx';
+import BundlePackages from "/snippets/bundle-packages.mdx";
 
 Let's take a look at a basic `trigger.config.ts` file. This is generated for you when you follow [the quick start guide](/quick-start). This file is used to configure your project and how it's bundled.
 
@@ -112,7 +112,7 @@ You can sync environment variables from another service using the `resolveEnvVar
 
 We'll let you know when running the CLI dev command if this is a problem. Some packages are ESM-only so they don't work directly from CJS when using Node.js. In that case you need to add them to the `dependenciesToBundle` array in your `trigger.config.ts` file.
 
-<BundlePackages/>
+<BundlePackages />
 
 ## Prisma (and other generators)
 

docs/config/extensions/custom.mdx

@@ -0,0 +1,5 @@
+---
+title: "Overview"
+sidebarTitle: "Overview"
+description: "This file is used to configure your project and how it's bundled."
+---

docs/config/extensions/esbuild-plugins.mdx

@@ -0,0 +1,5 @@
+---
+title: "Prisma"
+sidebarTitle: "Prisma"
+description: "This file is used to configure your project and how it's bundled."
+---

docs/config/extensions/overview.mdx

@@ -41,7 +41,7 @@ jobs:
         env:
           TRIGGER_ACCESS_TOKEN: ${{ secrets.TRIGGER_ACCESS_TOKEN }}
         run: |
-          npx trigger.dev@beta deploy
+          npx trigger.dev@latest deploy
 ```
 
 ```yaml .github/workflows/release-trigger-staging.yml
@@ -70,7 +70,7 @@ jobs:
         env:
           TRIGGER_ACCESS_TOKEN: ${{ secrets.TRIGGER_ACCESS_TOKEN }}
         run: |
-          npx trigger.dev@beta deploy --env staging
+          npx trigger.dev@latest deploy --env staging
 ```
 
 </CodeGroup>
@@ -81,16 +81,22 @@ If you already have a GitHub action file, you can just add the final step "🚀
 
 <Steps>
 
-<Step title="Create a new access token">Go to your profile page and click on the ["Personal Access Tokens"](https://cloud.trigger.dev/account/tokens) tab.</Step>
+<Step title="Create a new access token">
+  Go to your profile page and click on the ["Personal Access
+  Tokens"](https://cloud.trigger.dev/account/tokens) tab.
+</Step>
 
-<Step title="Go to your repository on GitHub.">Click on 'Settings' -> 'Secrets and variables' -> 'Actions' -> 'New repository secret'</Step>
+<Step title="Go to your repository on GitHub.">
+  Click on 'Settings' -> 'Secrets and variables' -> 'Actions' -> 'New repository secret'
+</Step>
 
-<Step title="Add the TRIGGER_ACCESS_TOKEN">Add the name `TRIGGER_ACCESS_TOKEN` and the value of your access token. ![Add TRIGGER_ACCESS_TOKEN in GitHub](/images/github-access-token.png)</Step>
+<Step title="Add the TRIGGER_ACCESS_TOKEN">
+  Add the name `TRIGGER_ACCESS_TOKEN` and the value of your access token. ![Add TRIGGER_ACCESS_TOKEN
+  in GitHub](/images/github-access-token.png)
+</Step>
 
 </Steps>
 
-
-
 ## Version pinning
 
 The CLI and `@trigger.dev/*` package versions need to be in sync, otherwise there will be errors and unpredictable behavior. Hence, the `deploy` command will automatically fail during CI on any version mismatches.
@@ -104,6 +110,7 @@ Tip: add the deploy command to your `package.json` file to keep versions managed
   }
 }
 ```
+
 Your workflow file will follow the version specified in the `package.json` script, like so:
 
 ```yaml .github/workflows/release-trigger.yml