document changes in pnpm 9.6

docs/catalogs.md

@@ -47,6 +47,13 @@ This is equivalent to writing a version range (e.g. `^18.3.1`) directly.
 }
 ```
 
+You may use the `catalog:` protocol in the next fields of your `package.json`:
+
+* `dependencies`
+* `devDependencies`
+* `optionalDependencies`
+* `pnpm.overrides`
+
 The `catalog:` protocol allows an optional name after the colon (ex: `catalog:name`) to specify which catalog should be used. When a name is omitted, the default catalog is used.
 
 Depending on the scenario, the `catalog:` protocol offers a few [advantages](#advantages) compared to writing version ranges directly that are detailed next.

docs/npmrc.md

@@ -844,6 +844,10 @@ Use this `.npmrc` file:
 use-node-version=16.16.0
 ```
 
+This setting works only in a `.npmrc` file that is in the root of your workspace. If you need to specify a custom Node.js for a project in the workspace, use the [`pnpm.executionEnv.nodeVersion`] field of `package.json` instead.
+
+[`pnpm.executionEnv.nodeVersion`]: ./package_json.md#pnpmexecutionenvnodeversion
+
 ### node-version
 
 * Default: the value returned by **node -v**, without the v prefix

docs/package_json.md

@@ -634,6 +634,26 @@ If an optional dependency has its name included in this array, it will be skippe
 }
 ```
 
+## pnpm.executionEnv.nodeVersion
+
+Added in: v9.6.0
+
+Specifies which exact Node.js version should be used for the project's runtime.
+pnpm will automatically install the specified version of Node.js and use it for
+running `pnpm run` commands or the `pnpm node` command.
+
+For example:
+
+```json
+{
+  "pnpm": {
+    "executionEnv": {
+      "nodeVersion": "16.16.0"
+    }
+  }
+}
+```
+
 ## resolutions
 
 Functionally identical to [`pnpm.overrides`], this field is intended to make it easier to migrate from Yarn.