Update config files for Rush 5.29.0

pages/configs/deploy_json.md

@@ -46,6 +46,16 @@ generates for **common/config/rush/deploy.json**:
    */
   // "includeNpmIgnoreFiles": true,
 
+  /**
+   * To improve backwards compatibility with legacy packages, the PNPM package manager installs extra links in the
+   * node_modules folder that enable packages to import undeclared dependencies.  In some cases this workaround may
+   * double the number of links created.  If your deployment does not require this workaround, you can set
+   * "omitPnpmWorkaroundLinks" to true to avoid creating the extra links.
+   *
+   * The default value is false.
+   */
+  // "omitPnpmWorkaroundLinks": true,
+
   /**
    * Specify how links (symbolic links, hard links, and/or NTFS junctions) will be created in the deployed folder:
    *
@@ -56,6 +66,13 @@ generates for **common/config/rush/deploy.json**:
    */
   // "linkCreation": "script",
 
+  /**
+   * If this path is specified, then after "rush deploy", recursively copy the files from this folder to
+   * the deployment target folder (common/deploy). This can be used to provide additional configuration files
+   * or scripts needed by the server when deploying. The path is resolved relative to the repository root.
+   */
+  //  "folderToCopy": "repo-tools/assets/deploy-config",
+
   /**
    * Customize how Rush projects are processed during deployment.
    */
@@ -72,6 +89,35 @@ generates for **common/config/rush/deploy.json**:
     //    */
     //   "additionalProjectsToInclude": [
     //     // "@my-scope/my-project2"
+    //   ],
+    //
+    //   /**
+    //    * When deploying a project, the included dependencies are normally determined automatically based on
+    //    * package.json fields such as "dependencies", "peerDependencies", and "optionalDependencies",
+    //    * subject to other deployment settings such as "includeDevDependencies".  However, in cases where
+    //    * that information is not accurate, you can use "additionalDependenciesToInclude" to add more
+    //    * packages to the list.
+    //    *
+    //    * The list can include any package name that is installed by Rush and resolvable via Node.js module
+    //    * resolution; however, if it resolves to a local Rush project, the "additionalProjectsToInclude"
+    //    * field will not be recursively applied.
+    //    */
+    //   "additionalDependenciesToInclude": [
+    //     // "@rushstack/node-core-library"
+    //   ],
+    //
+    //   /**
+    //    * This setting prevents specific dependencies from being deployed.  It only filters dependencies that
+    //    * are explicitly declared in package.json for this project.  It does not affect dependencies added
+    //    * via "additionalProjectsToInclude" or "additionalDependenciesToInclude", nor does it affect indirect
+    //    * dependencies.
+    //    *
+    //    * The "*" wildcard may be used to match zero or more characters.  For example, if your project already
+    //    * bundles its own dependencies, specify "dependenciesToExclude": [ "*" ] to exclude all package.json
+    //    * dependencies.
+    //    */
+    //   "dependenciesToExclude": [
+    //     // "@types/*"
     //   ]
     // }
   ]

pages/configs/rush_json.md

@@ -26,7 +26,7 @@ generates for **rush.json** (in the repo root folder):
    * path segment in the "$schema" field for all your Rush config files.  This will ensure
    * correct error-underlining and tab-completion for editors such as VS Code.
    */
-  "rushVersion": "5.26.0",
+  "rushVersion": "5.29.0",
 
   /**
    * The next field selects which package manager should be installed and determines its version.
@@ -36,7 +36,7 @@ generates for **rush.json** (in the repo root folder):
    * Specify one of: "pnpmVersion", "npmVersion", or "yarnVersion".  See the Rush documentation
    * for details about these alternatives.
    */
-  "pnpmVersion": "4.12.5",
+  "pnpmVersion": "4.14.4",
 
   // "npmVersion": "4.5.0",
   // "yarnVersion": "1.9.4",
@@ -104,7 +104,23 @@ generates for **rush.json** (in the repo root folder):
      *
      * The default value is false.
      */
-    // "preventManualShrinkwrapChanges": true
+    // "preventManualShrinkwrapChanges": true,
+
+    /**
+     * If true, then `rush install` will use the PNPM workspaces feature to perform the
+     * install.
+     *
+     * This feature uses PNPM to peform the entire monorepo install. When using workspaces, Rush will
+     * generate a "pnpm-workspace.yaml" file referencing all local projects to install. Rush will
+     * also generate a "pnpmfile.js" which is used to provide preferred versions support. When install
+     * is run, this pnpmfile will be used to replace dependency version ranges with a smaller subset
+     * of the original range. If the preferred version is not fully a subset of the original version
+     * range, it will be left as-is. After this, the pnpmfile.js provided in the repository (if one
+     * exists) will be called to further modify package dependencies.
+     *
+     * This option is experimental. The default value is false.
+     */
+    // "useWorkspaces": true
   },
 
   /**