fix: Update integration tests for daemon deprecation

anthonyshew · anthonyshew · commit 5b33e20e6baa · 2026-02-19T07:08:22.000-07:00
- Regenerate turbo-help.t from actual -h output (daemon flags hidden) - Restore --daemon/--no-daemon in bad-flag.t error usage (hide only affects help, not error hints) - Add deprecation warnings to config.t expected output - Remove --no-daemon from run-summary tests (no longer needed)
diff --git a/turborepo-tests/integration/tests/other/bad-flag.t b/turborepo-tests/integration/tests/other/bad-flag.t
@@ -46,6 +46,8 @@ Bad flag with an implied run command should display run flags
       --cache-workers <CACHE_WORKERS>
       --dry-run \[<DRY_RUN>\] (re)
       --graph \[<GRAPH>\] (re)
+      --daemon <DAEMON>
+      --no-daemon <NO_DAEMON>
       --profile [<PROFILE>]
       --anon-profile [<ANON_PROFILE>]
       --summarize \[<SUMMARIZE>\] (re)
diff --git a/turborepo-tests/integration/tests/other/turbo-help.t b/turborepo-tests/integration/tests/other/turbo-help.t
@@ -93,116 +93,32 @@ Test help flag
             Generate a summary of the turbo run [possible values: true, false]
         --parallel
             Execute all tasks in parallel
-    -h, --help
-            Print help (see a summary with '-h')
-  
-  Run Arguments:
-        --cache <CACHE>
-            Set the cache behavior for this run. Pass a list of comma-separated key, value pairs to enable reading and writing to either the local or remote cache
-  
-        --force [<FORCE>]
-            Ignore the existing cache (to force execution). Equivalent to `--cache=local:w,remote:w`
-            
-            [possible values: true, false]
-  
-        --remote-only [<REMOTE_ONLY>]
-            Ignore the local filesystem cache for all tasks. Only allow reading and caching artifacts using the remote cache. Equivalent to `--cache=remote:rw`
-            
-            [possible values: true, false]
-  
-        --remote-cache-read-only [<REMOTE_CACHE_READ_ONLY>]
-            Treat remote cache as read only. Equivalent to `--cache=remote:r;local:rw`
-            
-            [possible values: true, false]
-  
-        --no-cache
-            Avoid saving task results to the cache. Useful for development/watch tasks. Equivalent to `--cache=local:r,remote:r`
-  
-        --cache-workers <CACHE_WORKERS>
-            Set the number of concurrent cache operations (default 10)
-            
-            [default: 10]
-  
-        --dry-run [<DRY_RUN>]
-            [possible values: text, json]
-  
-        --graph [<GRAPH>]
-            Generate a graph of the task execution and output to a file when a filename is specified (.svg, .png, .jpg, .pdf, .json, .html, .mermaid, .dot). Outputs dot graph to stdout when if no filename is provided
-  
-        --profile [<PROFILE>]
-            File to write turbo's performance profile output into. You can load the file up in chrome://tracing to see which parts of your build were slow
-  
-        --anon-profile [<ANON_PROFILE>]
-            File to write turbo's performance profile output into. All identifying data omitted from the profile
-  
-        --summarize [<SUMMARIZE>]
-            Generate a summary of the turbo run
-            
-            [possible values: true, false]
-  
-        --parallel
-            Execute all tasks in parallel
-  
         --cache-dir <CACHE_DIR>
             Override the filesystem cache directory
-  
         --concurrency <CONCURRENCY>
             Limit the concurrency of task execution. Use 1 for serial (i.e. one-at-a-time) execution
-  
         --continue[=<CONTINUE>]
-            Specify how task execution should proceed when an error occurs. Use "never" to cancel all tasks. Use "dependencies-successful" to continue running tasks whose dependencies have succeeded. Use "always" to continue running all tasks, even those whose dependencies have failed
-            
-            [default: never]
-            [possible values: never, dependencies-successful, always]
-  
+            Specify how task execution should proceed when an error occurs. Use "never" to cancel all tasks. Use "dependencies-successful" to continue running tasks whose dependencies have succeeded. Use "always" to continue running all tasks, even those whose dependencies have failed [default: never] [possible values: never, dependencies-successful, always]
         --single-package
             Run turbo in single-package mode
-  
         --framework-inference [<BOOL>]
-            Specify whether or not to do framework inference for tasks
-            
-            [default: true]
-            [possible values: true, false]
-  
+            Specify whether or not to do framework inference for tasks [default: true] [possible values: true, false]
         --global-deps <GLOBAL_DEPS>
             Specify glob of global filesystem dependencies to be hashed. Useful for .env and files
-  
         --env-mode [<ENV_MODE>]
-            Environment variable mode. Use "loose" to pass the entire existing environment. Use "strict" to use an allowlist specified in turbo.json
-  
-            Possible values:
-            - loose:  Allow all environment variables for the process to be available
-            - strict: Filter environment variables to only those that are specified in the `env` and `globalEnv` keys in `turbo.json`
-  
+            Environment variable mode. Use "loose" to pass the entire existing environment. Use "strict" to use an allowlist specified in turbo.json [possible values: loose, strict]
     -F, --filter <FILTER>
             Use the given selector to specify package(s) to act as entry points. The syntax mirrors pnpm's syntax, and additional documentation and examples can be found in turbo's documentation https://turborepo.dev/docs/reference/command-line-reference/run#--filter
-  
         --affected
             Filter to only packages that are affected by changes between the current branch and `main`
-  
         --output-logs <OUTPUT_LOGS>
-            Set type of process output logging. Use "full" to show all output. Use "hash-only" to show only turbo-computed task hashes. Use "new-only" to show only new output with only hashes for cached tasks. Use "none" to hide process output. (default full)
-  
-            Possible values:
-            - full:        Displays all output
-            - none:        Hides all task output
-            - hash-only:   Show only the hashes of the tasks
-            - new-only:    Only show output from cache misses
-            - errors-only: Only show output from task failures
-  
+            Set type of process output logging. Use "full" to show all output. Use "hash-only" to show only turbo-computed task hashes. Use "new-only" to show only new output with only hashes for cached tasks. Use "none" to hide process output. (default full) [possible values: full, none, hash-only, new-only, errors-only]
         --log-order <LOG_ORDER>
-            Set type of task output order. Use "stream" to show output as soon as it is available. Use "grouped" to show output when a command has finished execution. Use "auto" to let turbo decide based on its own heuristics. (default auto)
-            
-            [possible values: auto, stream, grouped]
-  
+            Set type of task output order. Use "stream" to show output as soon as it is available. Use "grouped" to show output when a command has finished execution. Use "auto" to let turbo decide based on its own heuristics. (default auto) [possible values: auto, stream, grouped]
         --only
             Only executes the tasks specified, does not execute parent tasks
-  
         --log-prefix <LOG_PREFIX>
-            Use "none" to remove prefixes from task logs. Use "task" to get task id prefixing. Use "auto" to let turbo decide how to prefix the logs based on the execution environment. In most cases this will be the same as "task". Note that tasks running in parallel interleave their logs, so removing prefixes can make it difficult to associate logs with tasks. Use --log-order=grouped to prevent interleaving. (default auto)
-            
-            [default: auto]
-            [possible values: auto, none, task]
+            Use "none" to remove prefixes from task logs. Use "task" to get task id prefixing. Use "auto" to let turbo decide how to prefix the logs based on the execution environment. In most cases this will be the same as "task". Note that tasks running in parallel interleave their logs, so removing prefixes can make it difficult to associate logs with tasks. Use --log-order=grouped to prevent interleaving. (default auto) [default: auto] [possible values: auto, none, task]
 
 
 Test help flag for link command
