@rushstack/rush-sdk 5.107.1 → 5.107.2

package/dist/rush-lib.d.ts

@@ -2850,15 +2850,28 @@ export declare class PnpmOptionsConfiguration extends PackageManagerOptionsConfi
      */
     readonly pnpmStore: PnpmStoreLocation;
     /**
-     * This setting determines PNPM's `resolution-mode`  option. The default value is `highest`.
+     * This setting determines how PNPM chooses version numbers during `rush update`.
      *
      * @remarks
-     * Be aware that the PNPM 8 initially defaulted to `lowest` instead of  `highest`, but PNPM
-     * reverted this decision in 8.6.12 because it caused confusion for users.  Rush 5.106.0 and newer
-     * avoids this confusion by consistently defaulting to `highest` when `resolutionMode` is not
-     * explicitly set in pnpm-config.json or .npmrc, regardless of your PNPM version.
+     * For example, suppose `lib-x@3.0.0` depends on `"lib-y": "^1.2.3"` whose latest major
+     * releases are `1.8.9` and `2.3.4`.  The resolution mode `lowest-direct` might choose
+     * `lib-y@1.2.3`, wheres `highest` will choose 1.8.9, and `time-based` will pick the
+     * highest compatible version at the time when `lib-x@3.0.0` itself was published (ensuring
+     * that the version could have been tested by the maintainer of "lib-x").  For local workspace
+     * projects, `time-based` instead works like `lowest-direct`, avoiding upgrades unless
+     * they are explicitly requested. Although `time-based` is the most robust option, it may be
+     * slightly slower with registries such as npmjs.com that have not implemented an optimization.
+     *
+     * IMPORTANT: Be aware that PNPM 8.0.0 initially defaulted to `lowest-direct` instead of
+     * `highest`, but PNPM reverted this decision in 8.6.12 because it caused confusion for users.
+     * Rush version 5.106.0 and newer avoids this confusion by consistently defaulting to
+     * `highest` when `resolutionMode` is not explicitly set in pnpm-config.json or .npmrc,
+     * regardless of your PNPM version.
      *
      * PNPM documentation: https://pnpm.io/npmrc#resolution-mode
+     *
+     * Possible values are: `highest`, `time-based`, and `lowest-direct`.
+     * The default is `highest`.
      */
     readonly resolutionMode: PnpmResolutionMode | undefined;
     /**

package/lib/logic/pnpm/PnpmOptionsConfiguration.d.ts

@@ -116,15 +116,28 @@ export declare class PnpmOptionsConfiguration extends PackageManagerOptionsConfi
      */
     readonly pnpmStore: PnpmStoreLocation;
     /**
-     * This setting determines PNPM's `resolution-mode`  option. The default value is `highest`.
+     * This setting determines how PNPM chooses version numbers during `rush update`.
      *
      * @remarks
-     * Be aware that the PNPM 8 initially defaulted to `lowest` instead of  `highest`, but PNPM
-     * reverted this decision in 8.6.12 because it caused confusion for users.  Rush 5.106.0 and newer
-     * avoids this confusion by consistently defaulting to `highest` when `resolutionMode` is not
-     * explicitly set in pnpm-config.json or .npmrc, regardless of your PNPM version.
+     * For example, suppose `lib-x@3.0.0` depends on `"lib-y": "^1.2.3"` whose latest major
+     * releases are `1.8.9` and `2.3.4`.  The resolution mode `lowest-direct` might choose
+     * `lib-y@1.2.3`, wheres `highest` will choose 1.8.9, and `time-based` will pick the
+     * highest compatible version at the time when `lib-x@3.0.0` itself was published (ensuring
+     * that the version could have been tested by the maintainer of "lib-x").  For local workspace
+     * projects, `time-based` instead works like `lowest-direct`, avoiding upgrades unless
+     * they are explicitly requested. Although `time-based` is the most robust option, it may be
+     * slightly slower with registries such as npmjs.com that have not implemented an optimization.
+     *
+     * IMPORTANT: Be aware that PNPM 8.0.0 initially defaulted to `lowest-direct` instead of
+     * `highest`, but PNPM reverted this decision in 8.6.12 because it caused confusion for users.
+     * Rush version 5.106.0 and newer avoids this confusion by consistently defaulting to
+     * `highest` when `resolutionMode` is not explicitly set in pnpm-config.json or .npmrc,
+     * regardless of your PNPM version.
      *
      * PNPM documentation: https://pnpm.io/npmrc#resolution-mode
+     *
+     * Possible values are: `highest`, `time-based`, and `lowest-direct`.
+     * The default is `highest`.
      */
     readonly resolutionMode: PnpmResolutionMode | undefined;
     /**

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@rushstack/rush-sdk",
-  "version": "5.107.1",
+  "version": "5.107.2",
   "description": "An API for interacting with the Rush engine",
   "repository": {
     "type": "git",
@@ -30,13 +30,13 @@
   "devDependencies": {
     "@types/semver": "7.5.0",
     "@types/webpack-env": "1.18.0",
-    "@microsoft/rush-lib": "5.107.1",
+    "@microsoft/rush-lib": "5.107.2",
     "@rushstack/eslint-config": "3.3.4",
-    "@rushstack/heft": "0.60.0",
+    "@rushstack/heft": "0.61.0",
     "local-node-rig": "1.0.0",
-    "@rushstack/stream-collator": "4.1.2",
+    "@rushstack/stream-collator": "4.1.3",
     "@rushstack/ts-command-line": "4.16.0",
-    "@rushstack/terminal": "0.7.1"
+    "@rushstack/terminal": "0.7.2"
   },
   "scripts": {
     "build": "heft build --clean",