Update for --profile flag.

docs/pages/repo/docs/reference/command-line-reference/run.mdx

@@ -348,6 +348,8 @@ turbo run dev --parallel --no-cache
 Generates a trace of the run in Chrome Tracing format that you can use to analyze performance.
 The profile can be viewed in [Perfetto](https://ui.perfetto.dev/).
 
+You must provide a verbosity flag (`-v`, `-vv`, or `-vvv`) with the `--profile` to produce a trace.
+
 ```sh
 turbo run build --profile=profile.json
 ```
@@ -406,35 +408,32 @@ turbo run build --preflight
 
 The same behavior can also be set via the `TURBO_PREFLIGHT=true` environment variable.
 
-### `--trace`
-
-`type: string`
+### `--verbosity`
 
-To view CPU trace, outputs the trace to the given file, use `go tool trace [file]`.
+To specify log level, use `--verbosity=<num>` or `-v, -vv, -vvv`.
 
-<Callout>
-  **Important**: The trace viewer doesn't work under Windows Subsystem for
-  Linux.
-</Callout>
+- `Info `: `--verbosity=1`, or `-v`
+- `Debug`: `--verbosity=2`, or `-vv`
+- `Trace`: `--verbosity=3`, or `-vvv`
 
 ```sh
-turbo run build --trace="<trace-file-name>"
+turbo run build -v
+turbo run build --verbosity=2
+turbo run build -vvv
 ```
 
-### `--heap`
-
-`type: string`
-
-To view heap trace, outputs the trace to the given file, use `go tool pprof [file]` and type `top`. You can also drop it into [speedscope](https://www.speedscope.app/) and use the `left heavy` or `sandwich` view modes.
-
-```sh
-turbo run build --heap="<heap-file-name>"
-```
+## Deprecated Options
 
 ### `--cpuprofile`
 
 `type: string`
 
+<Callout type="error">
+  `--cpuprofile` is deprecated in `1.11.x`. Please use
+  [`--profile`](#--profile)
+  instead.
+</Callout>
+
 To view CPU profile, outputs the profile to the given file, drop the file into [speedscope](https://www.speedscope.app/).
 
 <Callout>
@@ -447,22 +446,6 @@ To view CPU profile, outputs the profile to the given file, drop the file into [
 turbo run build --cpuprofile="<cpu-profile-file-name>"
 ```
 
-### `--verbosity`
-
-To specify log level, use `--verbosity=<num>` or `-v, -vv, -vvv`.
-
-- `Info `: `--verbosity=1`, or `-v`
-- `Debug`: `--verbosity=2`, or `-vv`
-- `Trace`: `--verbosity=3`, or `-vvv`
-
-```sh
-turbo run build -v
-turbo run build --verbosity=2
-turbo run build -vvv
-```
-
-## Deprecated Options
-
 ### `--include-dependencies`
 
 <Callout type="error">
@@ -502,6 +485,21 @@ cached. Then, you change a line of code in B. With the `--deps` flag on, running
 because they are not impacted by the change. If you were to run
 `turbo run build --no-deps` instead, turbo will only run `build` in B.
 
+### `--heap`
+
+<Callout type="error">
+  `--heap` is deprecated in `1.2.x`. Please use
+  [`--profile`](#--profile) instead.
+</Callout>
+
+`type: string`
+
+To view heap trace, outputs the trace to the given file, use `go tool pprof [file]` and type `top`. You can also drop it into [speedscope](https://www.speedscope.app/) and use the `left heavy` or `sandwich` view modes.
+
+```sh
+turbo run build --heap="<heap-file-name>"
+```
+
 ### `--scope`
 
 <Callout type="error">
@@ -539,6 +537,27 @@ turbo run build --since=origin/main
   input files for a workspace exist inside their respective workspace folders.
 </Callout>
 
+### `--trace`
+
+<Callout type="error">
+  `--trace` is deprecated in `1.11.x`, use
+  [`--profile`](#--profile)
+  instead.
+</Callout>
+
+`type: string`
+
+To view CPU trace, outputs the trace to the given file, use `go tool trace [file]`.
+
+<Callout>
+  **Important**: The trace viewer doesn't work under Windows Subsystem for
+  Linux.
+</Callout>
+
+```sh
+turbo run build --trace="<trace-file-name>"
+```
+
 [1]: /repo/docs/reference/configuration#passThroughEnv
 [2]: /repo/docs/reference/configuration#globalPassThroughEnv
 [3]: /repo/docs/core-concepts/monorepos/filtering

profile.json

@@ -0,0 +1,3 @@
+[
+
+]