docs(deploy): flag and setting for legacy

docs/cli/deploy.md

@@ -5,6 +5,12 @@ title: "pnpm deploy"
 
 Deploy a package from a workspace. During deployment, the files of the deployed package are copied to the target directory. All dependencies of the deployed package, including dependencies from the workspace, are installed inside an isolated `node_modules` directory at the target directory. The target directory will contain a portable package that can be copied to a server and executed without additional steps.
 
+:::note
+
+By default, the deploy command only works with workspaces that have the `injected-workspace-dependencies` setting set to `true`. If you want to use deploy without "injected dependencies", use the `--legacy` flag or set `force-legacy-deploy` to `true`.
+
+:::
+
 Usage:
 
 ```
@@ -53,6 +59,12 @@ Packages in `devDependencies` won't be installed.
 
 [Read more about filtering.](../filtering.md)
 
+### --legacy
+
+Force legacy deploy implementation.
+
+By default, `pnpm deploy` will try creating a dedicated lockfile from a shared lockfile for deployment. The `--legacy` flag disables this behavior and also allows using the deploy command without the `injected-workspace-dependencies=true` setting.
+
 ## Files included in the deployed project
 
 By default, all the files of the project are copied during deployment but this can be modified in _one_ of the following ways which are resolved in order:

docs/npmrc.md

@@ -1019,6 +1019,15 @@ When set to `true`, no workspace cycle warnings will be printed.
 
 When set to `true`, installation will fail if the workspace has cycles.
 
+## Deploy Settings
+
+### force-legacy-deploy
+
+* Default: **false**
+* Type: **Boolean**
+
+By default, `pnpm deploy` will try creating a dedicated lockfile from a shared lockfile for deployment. If this setting is set to `true`, the legacy `deploy` behavior will be used.
+
 ## Other Settings
 
 ### save-prefix