pnpm 12.16.1 → 12.17.0

package/CHANGELOG.md

@@ -1,5 +1,106 @@
 # pnpm
 
+## 12.17.0
+
+pnpm 12.17.0 adds `pnpm peers check --global`, dependency-group selectors and wildcards in `overrides`, and runtime, package manager, Cargo, and Python updates in `pnpm outdated` and `pnpm update`. It also fixes files that other users could not read in Docker images, and repeat installs that missed changes to local dependencies.
+
+### Minor Changes
+
+- `pnpm peers check` now accepts `--global` (`-g`) to check globally installed packages. After a global install or update, the peer dependency warning now suggests `pnpm peers check -g` [#17504](https://github.com/pnpm/pnpm/issues/17504).
+
+- `pnpm outdated` and `pnpm update` now inspect and update package manager and runtime versions in `devEngines.packageManager`, `packageManager`, `devEngines.runtime`, `engines.runtime`, and `runtime:` dependencies. With `cargo.enabled` or `python.enabled`, `pnpm outdated` and `pnpm update` also inspect and update Cargo dependencies in `Cargo.toml` and `Cargo.lock` and Python dependencies in `pyproject.toml` and `pylock.toml`.
+
+- `overrides` selectors now support `:prod`, `:optional`, and `:peer` pseudo-selectors that target a single dependency group. They also support `*` wildcard patterns on parent and target package names. An override with a non-range value, such as `npm:` or `file:`, no longer adds a peer dependency to `dependencies`. Removing an optional dependency with `"-"` now also removes the duplicate entry from `dependencies` [#5391](https://github.com/pnpm/pnpm/issues/5391).
+
+### Patch Changes
+
+#### Installing packages
+
+- Files that pnpm creates in a project now get the permissions the umask gives any new file, such as `0644`. Before, several of them were readable only by the user who ran pnpm, which broke Docker images that run as a different user [#17435](https://github.com/orgs/pnpm/discussions/17435).
+
+  The fix applies to:
+
+  - `node_modules/.pnpm-workspace-state-v1.json`. A different user running `pnpm run` reinstalled the dependencies because it could not read this file.
+  - `pnpm-workspace.yaml`
+  - the files written by `pnpm deploy`
+  - patch files from `pnpm patch-commit`
+  - the lockfile restored by `pnpm dedupe --check`
+  - the Cargo and Python files that pnpm writes
+
+  When pnpm edits an existing file, the file keeps its permissions.
+
+- `pnpm install` no longer writes broken dependency links when the project's `node_modules` is a symlink to another directory, such as another project's `node_modules`. The install reported success, but the links it wrote did not resolve [#17448](https://github.com/pnpm/pnpm/issues/17448).
+
+- Commands installed with `pnpm add --global` now find the dependencies that pnpm hoists for their package. A package that loads a dependency it does not declare, such as a native addon's platform-specific package, failed with "Cannot find module". Reinstall such a package with `pnpm add --global` to update its existing command [#17503](https://github.com/pnpm/pnpm/issues/17503).
+
+- When pnpm switches to the version a project pins, it now installs that version's native binary for the current host, even if the project's `supportedArchitectures` excludes the host. Before, pnpm could not use the pinned version and kept running the installed one. pnpm also repairs a pinned version that an earlier install left without the host's binary.
+
+- With the global virtual store, a change to a dependency of one package in a dependency cycle now gives every package in that cycle a new directory. Before, the other packages kept their directories and still linked the old copy of the changed package, so the project could load two copies of it [#17466](https://github.com/pnpm/pnpm/issues/17466).
+
+  Packages in a dependency cycle, and packages that depend on one, move to new global virtual store directories once after this update. Those that run a build miss the side-effects cache once.
+
+- With `nodeLinker: hoisted`, when two workspace projects need the same package version and it cannot be hoisted to the root, each project now keeps the copy installed in its own `node_modules`. Build scripts run in each of these copies. Before, the second project's copy was replaced with a symlink to the first project's, so every repeat install imported it again [#17498](https://github.com/pnpm/pnpm/issues/17498).
+
+- The Node.js `latest` selector now chooses the newest stable release [#17490](https://github.com/pnpm/pnpm/issues/17490).
+
+- Hardlinking from the store now stats each store file once per install. Since pnpm 12.8.0, a store file was stat'ed again for every package that links it. On an offline install of a large workspace, that added up to 15% system CPU [#17500](https://github.com/pnpm/pnpm/issues/17500).
+
+#### Repeat installs and local dependencies
+
+- `pnpm install --frozen-lockfile` no longer reports an outdated lockfile right after the install that wrote it. This happened when a pnpmfile `readPackage` hook or `packageExtensions` changed the dependencies or peer dependencies of a local directory dependency outside the workspace projects. It affected a `file:` dependency, an injected `workspace:../dir` dependency outside the workspace patterns, and an injected workspace package left out by `--filter` [#17447](https://github.com/pnpm/pnpm/issues/17447) [#17473](https://github.com/pnpm/pnpm/issues/17473).
+
+  A repeat `pnpm install` now takes the fast path when `ignoredOptionalDependencies` removes an optional dependency of a `file:` directory dependency. It used to resolve again on every run.
+
+- `pnpm install` now resolves again after an edit to an injected `workspace:../dir` dependency outside the workspace patterns under a shared lockfile. It used to keep the lockfile unchanged. The next `pnpm install --frozen-lockfile` then failed [#17476](https://github.com/pnpm/pnpm/issues/17476).
+
+- `pnpm install` now resolves a local directory again after its `package.json` changes when an override or a package extension adds it to the dependencies of a registry package. `pnpm install --frozen-lockfile` fails on a lockfile that still records the old dependencies of such a directory [#17486](https://github.com/pnpm/pnpm/issues/17486).
+
+- With `injectWorkspacePackages` and per-project lockfiles, `pnpm install` now updates a project's lockfile when a local tarball that an injected workspace project depends on is replaced. The project's lockfile kept the old version and integrity before.
+
+- `pnpm install` now detects a change to a local tarball or directory that only a pnpmfile `readPackage` hook depends on. A repeat install reported "Already up to date" and kept the old contents before [pnpm/tasks#227](https://github.com/pnpm/tasks/issues/227).
+
+- `pnpm install` now relinks a `workspace:` or `link:` dependency whose link was deleted from `node_modules`. It used to report "Already up to date" and leave the link missing [#17485](https://github.com/pnpm/pnpm/issues/17485).
+
+- A repeat `pnpm install` reports "Already up to date" again when a pnpmfile `readPackage` hook changes the dependencies of a workspace project. Since 12.15.0, every such install ran in full [#17468](https://github.com/pnpm/pnpm/issues/17468).
+
+  After an edit to a project's `package.json`, `pnpm install` and `verifyDepsBeforeRun` now run the pnpmfile's `readPackage` hook on the edited manifest before comparing it with the lockfile. They could report the project up to date when the hook rewrote the edited dependency to a specifier the lockfile did not record.
+
+#### Adding and updating dependencies
+
+- `pnpm update --latest` with package selectors now updates the dependencies of the selected packages within their declared ranges. Excluded packages and their dependencies keep their locked versions [#17444](https://github.com/pnpm/pnpm/issues/17444).
+
+- `pnpm add <pkg>@<tag>` now uses a catalog entry set to that same dist-tag. The dependency is saved as `catalog:` and the entry stays as written [pnpm/tasks#225](https://github.com/pnpm/tasks/issues/225).
+
+  When `pnpm add` adds a new dist-tag such as `vue@legacy` to a catalog, the catalog entry records the exact version the tag points to. The same applies to a dependency added without a version when the `tag` setting names a dist-tag other than `latest`.
+
+- `pnpm add` now saves the resolved version range of an npm alias. For example, `pnpm add v2@npm:vue` and `pnpm add v2@npm:vue@^3.0.0` both save `npm:vue@^3.5.13`.
+
+#### Running scripts and commands
+
+- Programs that a script or `pnpm exec` command leaves running, such as a browser opened by the `open` package, now outlive pnpm exactly when they would outlive the command run without pnpm. Before, on Windows, a failed command, `Ctrl+C`, or a closed terminal ended all of them. pnpm still ends them when it is killed or crashes.
+
+  When a recursive or parallel run bails, the scripts still running now receive `SIGTERM` on Unix and are killed only if they are still running two seconds later. On Windows, everything those scripts started is ended, including detached processes whose parent has already exited. Before, a bail killed them at once [#17465](https://github.com/pnpm/pnpm/issues/17465).
+
+- On Windows, the shell shim of a `.cmd` or `.bat` bin now runs it under Git Bash when MSYS argument conversion is off, such as with `MSYS_NO_PATHCONV=1` or `MSYS2_ARG_CONV_EXCL='*'`. The shim used to start an interactive cmd.exe prompt [#17480](https://github.com/pnpm/pnpm/issues/17480).
+
+- `pnx` and `pnpm create` now run the command in the directory selected by `--dir` or `--workspace-root`. Without either flag, the command still runs in the directory pnpm was started in.
+
+- `pnpm --env-file` now reads files the way `node --env-file` does. Values are taken as written, so `$VAR` is no longer expanded and Windows paths such as `C:\Users\me` load unchanged. A file is no longer rejected for its contents.
+
+#### Settings and messages
+
+- `pnpm version` no longer creates a git commit and tag when `gitTagVersion` is set to `false` [#17460](https://github.com/pnpm/pnpm/issues/17460).
+
+- `pnpm publish` now reads the `publishBranch` setting from `pnpm-workspace.yaml` and from `PNPM_CONFIG_PUBLISH_BRANCH`. The `--publish-branch` flag overrides it.
+
+- `pnpm` now accepts `--strict-ssl` and `--local-address <ip>` on the command line.
+
+- `pnpm doctor` uses a 15-second timeout when checking registry connectivity.
+
+- `pnpm-workspace.yaml` parse errors now report `ERR_PNPM_INVALID_SETTING`.
+
+- The error for a dependency with an invalid name in a project's manifest now names the project's directory. It used to say only "The current package", which did not tell which workspace project to fix [#17475](https://github.com/pnpm/pnpm/issues/17475).
+
 ## 12.16.1
 
 This release fixes `pnpm install` hanging on a cold store in workspaces that install Cargo crates, and `pnpm pack` shipping a file that `files` excludes by name.

package/README.md

@@ -65,6 +65,15 @@ To quote the [Rush](https://rushjs.io/) team:
           </picture>
         </a>
       </td>
+      <td align="center" valign="middle">
+        <a href="https://www.cloudflare.com/?utm_source=pnpm&utm_medium=readme" target="_blank" rel="noopener noreferrer">
+          <picture>
+            <source media="(prefers-color-scheme: light)" srcset="https://pnpm.io/img/users/cloudflare.svg" />
+            <source media="(prefers-color-scheme: dark)" srcset="https://pnpm.io/img/users/cloudflare_light.svg" />
+            <img src="https://pnpm.io/img/users/cloudflare.svg" width="160" alt="Cloudflare" />
+          </picture>
+        </a>
+      </td>
     </tr>
   </tbody>
 </table>
@@ -138,6 +147,15 @@ To quote the [Rush](https://rushjs.io/) team:
       <td align="center" valign="middle">
         <a href="https://latitude.so/?utm_source=pnpm&utm_medium=readme" target="_blank" rel="noopener noreferrer"><img src="https://pnpm.io/img/users/latitude.svg" width="160" alt="Latitude"></a>
       </td>
+      <td align="center" valign="middle">
+        <a href="https://syntax.fm/?utm_source=pnpm&utm_medium=readme" target="_blank" rel="noopener noreferrer">
+          <picture>
+            <source media="(prefers-color-scheme: light)" srcset="https://pnpm.io/img/users/syntaxfm.svg" />
+            <source media="(prefers-color-scheme: dark)" srcset="https://pnpm.io/img/users/syntaxfm_light.svg" />
+            <img src="https://pnpm.io/img/users/syntaxfm.svg" width="90" alt="Syntax" />
+          </picture>
+        </a>
+      </td>
     </tr>
   </tbody>
 </table>

package/dist/node_modules/.pnpm-workspace-state-v1.json

@@ -1,9 +1,9 @@
 {
-  "lastValidatedTimestamp": 1793108148932,
+  "lastValidatedTimestamp": 1793364144621,
   "projects": {
     "/home/runner/_work/pnpm/pnpm/pnpm/npm/pnpm/temp-deploy": {
       "name": "pacquet",
-      "version": "12.16.1",
+      "version": "12.17.0",
       "hasModulesDir": true
     }
   },
@@ -21,6 +21,7 @@
     },
     "autoInstallPeers": true,
     "catalogs": {},
+    "dangerouslyAllowAllBuilds": false,
     "dedupeDirectDeps": false,
     "dedupeInjectedDeps": false,
     "dedupePeerDependents": false,
@@ -82,6 +83,10 @@
     "preferWorkspacePackages": false,
     "production": true,
     "publicHoistPattern": [],
+    "registryRoutes": {
+      "@jsr": "https://npm.jsr.io/",
+      "@pnpm": "https://registry.npmjs.org/"
+    },
     "trustPolicy": "no-downgrade",
     "trustPolicyExclude": [
       "@pnpm/*",
@@ -91,6 +96,7 @@
       "undici-types@6.21.0"
     ],
     "trustPolicyIgnoreAfter": 10080,
+    "virtualStoreDirMaxLength": 120,
     "workspacePackagePatterns": [
       ".meta-updater",
       "pnpm11/__typecheck__",
@@ -162,24 +168,27 @@
     ]
   },
   "validation": {
-    "recordedAtNs": 1793108148932732288,
+    "recordedAtNs": 1793364144621578968,
     "files": {
       "/home/runner/_work/pnpm/pnpm/pnpm/npm/pnpm/temp-deploy/../../../../.config/pnpm/patches/graceful-fs@4.2.11.patch": {
-        "mtimeNs": 1793108123320725018,
-        "ctimeNs": 1793108123320725018,
+        "mtimeNs": 1793364126597573401,
+        "ctimeNs": 1793364126597573401,
         "size": 671,
         "digest": "68ebc232025360cb3dcd3081f4067f4e"
       },
       "/home/runner/_work/pnpm/pnpm/pnpm/npm/pnpm/temp-deploy/pnpm-lock.yaml": {
-        "mtimeNs": 1793108148656732208,
-        "ctimeNs": 1793108148656732208,
+        "mtimeNs": 1793364144445578912,
+        "ctimeNs": 1793364144445578912,
         "size": 6001,
         "digest": "b251eb0d29c262f40cbf984a99f53fb8"
       }
     },
     "lockfile": "b251eb0d29c262f40cbf984a99f53fb8",
     "manifests": {
-      ".": "48a2e9f48c9ba15435360444fd678acc"
+      ".": "2d48f551c25a522720cb8473e07df6a2"
+    },
+    "workspaceBins": {
+      ".": "fbddc193afab8e95acb4f0d48b0ca9c9"
     }
   }
 }

package/dist/node_modules/get-pnpm/lib/install.js

@@ -2,6 +2,7 @@ import { spawnSync } from 'node:child_process';
 import fs from 'node:fs';
 import os from 'node:os';
 import path from 'node:path';
+import semver from 'semver';
 import { extractTarball } from './extractTarball.js';
 import { registryConfigFromEnv } from './npmConfig.js';
 import { isMusl, platformPackageName } from './platformPackageName.js';
@@ -23,7 +24,9 @@ const UNPACK_DIR = '.unpack';
 function wrapperPackageName(major) {
     return major >= 12 ? CLI_PKG_NAME : '@pnpm/exe';
 }
-const USAGE = `Usage: npx get-pnpm [version]
+/** The first pnpm whose `pnpm setup` has `--no-modify-path`. */
+const NO_MODIFY_PATH_SINCE = '12.16.0';
+const USAGE = `Usage: npx get-pnpm [--no-modify-path] [version]
 
 Installs pnpm as a standalone executable and adds it to your PATH.
 
@@ -39,8 +42,15 @@ Arguments:
                      range resolves to the version pnpm-lock.yaml records
                      while that is still in range.
 
+Options:
+  --no-modify-path   Install pnpm without adding it to PATH: leave the shell
+                     config file and the Windows registry unchanged, and print
+                     the lines to add instead. Needs pnpm ${NO_MODIFY_PATH_SINCE} or
+                     newer.
+
 Environment variables:
   PNPM_VERSION           Version to install when no argument is given.
+  PNPM_NO_MODIFY_PATH    Set to 1 for the same as --no-modify-path.
   PNPM_HOME              Directory to install pnpm into.
   npm_config_registry    Registry to download pnpm from.
   npm_config_*:_authToken
@@ -56,11 +66,28 @@ Environment variables:
                          Node 24.14 or later.
 `;
 export async function runCli(argv) {
+    const args = parseCliArgs(argv, process.env);
+    if (args.help) {
+        console.log(USAGE);
+        return 0;
+    }
+    const registryConfig = registryConfigFromEnv();
+    return installPnpm({
+        versionSpec: args.version ?? process.env.PNPM_VERSION ?? projectVersionSpec(process.cwd()) ?? 'latest',
+        modifyPath: args.modifyPath,
+        ...registryConfig,
+    });
+}
+/** The command line, with `PNPM_NO_MODIFY_PATH` as the default of `--no-modify-path`. */
+export function parseCliArgs(argv, env) {
     const positional = [];
+    let modifyPath = !isEnabled(env.PNPM_NO_MODIFY_PATH);
     for (const arg of argv) {
-        if (arg === '--help' || arg === '-h') {
-            console.log(USAGE);
-            return 0;
+        if (arg === '--help' || arg === '-h')
+            return { help: true, modifyPath };
+        if (arg === '--no-modify-path') {
+            modifyPath = false;
+            continue;
         }
         if (arg.startsWith('-')) {
             throw new Error(`Unknown option "${arg}".\n\n${USAGE}`);
@@ -70,11 +97,11 @@ export async function runCli(argv) {
     if (positional.length > 1) {
         throw new Error(`Expected at most one version, got ${positional.length}.\n\n${USAGE}`);
     }
-    const registryConfig = registryConfigFromEnv();
-    return installPnpm({
-        versionSpec: positional[0] ?? process.env.PNPM_VERSION ?? projectVersionSpec(process.cwd()) ?? 'latest',
-        ...registryConfig,
-    });
+    return { help: false, version: positional[0], modifyPath };
+}
+/** Whether an on/off environment variable is on: set to anything but "", "0", or "false". */
+function isEnabled(value) {
+    return value != null && value !== '' && value !== '0' && value.toLowerCase() !== 'false';
 }
 /** The version `readProjectPin` finds for `dir`, saying where it comes from. */
 function projectVersionSpec(dir) {
@@ -96,6 +123,10 @@ function projectVersionSpec(dir) {
  * https://get.pnpm.io/install.sh downloads — the executable next to its `dist/`
  * tree — because `pnpm setup` installs that directory as-is.
  *
+ * With `modifyPath: false`, `pnpm setup --no-modify-path` leaves the shell
+ * config and the Windows registry alone. A pnpm whose setup lacks that option
+ * is refused before setup runs.
+ *
  * @returns the exit code of `pnpm setup`.
  */
 export async function installPnpm(opts) {
@@ -116,13 +147,19 @@ export async function installPnpm(opts) {
         process.once(signal, onSignal);
     }
     try {
-        const { binPath } = await downloadPnpm({ ...opts, dest: tmpDir });
-        const { error, status } = spawnSync(binPath, ['setup', '--force'], { stdio: 'inherit' });
+        const { version, binPath } = await downloadPnpm({ ...opts, dest: tmpDir });
+        const modifyPath = opts.modifyPath ?? true;
+        const setupArgs = [...setupCommand(version), '--force'];
+        if (!modifyPath) {
+            assertSetupCanLeavePathAlone(version);
+            setupArgs.push('--no-modify-path');
+        }
+        const { error, status } = spawnSync(binPath, setupArgs, { stdio: 'inherit' });
         if (error != null)
             throw error;
         if (status === 0) {
-            console.log(renderUndoHint(pnpmHomeDir()));
-            warnIfPnpmIsShadowed();
+            console.log(renderUndoHint(pnpmHomeDir(), process.platform, { modifiedPath: modifyPath }));
+            warnIfPnpmIsShadowed({ modifiedPath: modifyPath });
         }
         return status ?? 1;
     }
@@ -133,16 +170,34 @@ export async function installPnpm(opts) {
         removeTmpDir();
     }
 }
+/**
+ * The versions whose `pm` prefix forces a built-in command. pnpm 12.0.0 was
+ * released without it.
+ */
+const PM_PREFIX_VERSIONS = '>=11.0.0-beta.6 <12.0.0-0 || >=12.1.0';
+/**
+ * How to invoke the built-in `pnpm setup` of pnpm `version`. From pnpm 11, a
+ * `setup` script in the project the installer runs from can replace the
+ * built-in unless the `pm` prefix forces it.
+ */
+export function setupCommand(version) {
+    return semver.satisfies(version, PM_PREFIX_VERSIONS, { includePrerelease: true }) ? ['pm', 'setup'] : ['setup'];
+}
+function assertSetupCanLeavePathAlone(version) {
+    if (semver.lt(version, NO_MODIFY_PATH_SINCE)) {
+        throw new Error(`pnpm ${version} cannot be installed without adding it to PATH: --no-modify-path needs pnpm ${NO_MODIFY_PATH_SINCE} or newer. Install a newer pnpm, or leave out --no-modify-path.`);
+    }
+}
 /**
  * Says so when the pnpm `pnpm setup` just installed is not the one PATH
  * resolves, or the success above is the last thing the person reads before
  * `pnpm --version` prints the old version again.
  */
-function warnIfPnpmIsShadowed() {
+function warnIfPnpmIsShadowed(opts) {
     const pnpmHome = pnpmHomeDir();
     const shadowing = findShadowingPnpm(pnpmHome, { pathEnv: readPathEnv(process.env) });
     if (shadowing != null) {
-        console.error(renderShadowingPnpmWarning(shadowing, pnpmHome));
+        console.error(renderShadowingPnpmWarning(shadowing, pnpmHome, opts));
     }
 }
 /** Windows spells the variable `Path`, and the environment is case-insensitive there. */

package/dist/node_modules/get-pnpm/lib/shadowingPnpm.js

@@ -65,9 +65,10 @@ export function findShadowingPnpm(pnpmHome, opts) {
 }
 /**
  * The warning to print once `pnpm setup` installed under `pnpmHome` and
- * `shadowing` still answers to `pnpm`.
+ * `shadowing` still answers to `pnpm`. Without `modifiedPath`, setup left the
+ * shell config alone, so no new shell adds `$PNPM_HOME/bin` by itself.
  */
-export function renderShadowingPnpmWarning(shadowing, pnpmHome) {
+export function renderShadowingPnpmWarning(shadowing, pnpmHome, { modifiedPath = true } = {}) {
     const bin = path.join(pnpmHome, 'bin');
     const origin = ORIGIN_DESCRIPTIONS[shadowing.origin];
     const reorder = `move ${bin} ahead of ${path.dirname(shadowing.executable)} in PATH`;
@@ -78,8 +79,9 @@ export function renderShadowingPnpmWarning(shadowing, pnpmHome) {
             `Your shell keeps running that pnpm, not the one pnpm installed to ${bin}.\n` +
             `To finish switching, ${fix}.`;
     }
+    const when = modifiedPath ? 'Once a new shell adds it' : 'When you add it';
     return `Warning: "pnpm" on PATH is ${shadowing.executable} (${origin}), and ${bin} is not on PATH yet.\n` +
-        `Once a new shell adds it, it has to come first: ${fix}.`;
+        `${when}, it has to come first: ${fix}.`;
 }
 export function detectInstallOrigin(executable) {
     return originFromPath(realpathOrSelf(executable)) ??

package/dist/node_modules/get-pnpm/lib/undoHint.js

@@ -2,11 +2,14 @@
  * How to take back what `pnpm setup` just did under `pnpmHome`, printed once
  * it succeeds. `pnpm setup` names the shell config file it changed and prints
  * the lines it added, so the hint points back at that output rather than
- * guessing the file again.
+ * guessing the file again. Without `modifiedPath`, setup changed nothing but
+ * `pnpmHome`.
  */
-export function renderUndoHint(pnpmHome, platform = process.platform) {
-    const undo = platform === 'win32'
-        ? `delete ${pnpmHome}, then remove the PNPM_HOME variable and the Path entry pnpm setup added from your user environment variables.`
-        : `delete ${pnpmHome} and the lines pnpm setup added to the shell config file named above.`;
+export function renderUndoHint(pnpmHome, platform = process.platform, { modifiedPath = true } = {}) {
+    const undo = !modifiedPath
+        ? `delete ${pnpmHome}.`
+        : platform === 'win32'
+            ? `delete ${pnpmHome}, then remove the PNPM_HOME variable and the Path entry pnpm setup added from your user environment variables.`
+            : `delete ${pnpmHome} and the lines pnpm setup added to the shell config file named above.`;
     return `To uninstall, ${undo}\nSee https://pnpm.io/uninstall`;
 }

package/dist/node_modules/get-pnpm/package.json

@@ -1,6 +1,6 @@
 {
   "name": "get-pnpm",
-  "version": "0.0.10",
+  "version": "0.0.11",
   "private": true,
   "description": "Installs pnpm as a standalone executable",
   "keywords": [

package/package.json

@@ -9,7 +9,7 @@
       "./dist/node_modules/node-gyp/gyp/gyp"
     ]
   },
-  "version": "12.16.1",
+  "version": "12.17.0",
   "description": "Fast, disk space efficient package manager",
   "keywords": [
     "pnpm",
@@ -46,20 +46,20 @@
     "THIRD-PARTY-NOTICES.md"
   ],
   "optionalDependencies": {
-    "@pnpm/exe.win32-x64": "12.16.1",
-    "@pnpm/exe.win32-arm64": "12.16.1",
-    "@pnpm/exe.darwin-x64": "12.16.1",
-    "@pnpm/exe.darwin-arm64": "12.16.1",
-    "@pnpm/exe.linux-x64": "12.16.1",
-    "@pnpm/exe.linux-arm64": "12.16.1",
-    "@pnpm/exe.linux-riscv64": "12.16.1",
-    "@pnpm/exe.linux-ppc64": "12.16.1",
-    "@pnpm/exe.linux-s390x": "12.16.1",
-    "@pnpm/exe.linux-x64-musl": "12.16.1",
-    "@pnpm/exe.linux-arm64-musl": "12.16.1",
-    "@pnpm/exe.freebsd-x64": "12.16.1",
-    "@pnpm/exe.android-arm64": "12.16.1",
-    "@pnpm/exe.android-x64": "12.16.1"
+    "@pnpm/exe.win32-x64": "12.17.0",
+    "@pnpm/exe.win32-arm64": "12.17.0",
+    "@pnpm/exe.darwin-x64": "12.17.0",
+    "@pnpm/exe.darwin-arm64": "12.17.0",
+    "@pnpm/exe.linux-x64": "12.17.0",
+    "@pnpm/exe.linux-arm64": "12.17.0",
+    "@pnpm/exe.linux-riscv64": "12.17.0",
+    "@pnpm/exe.linux-ppc64": "12.17.0",
+    "@pnpm/exe.linux-s390x": "12.17.0",
+    "@pnpm/exe.linux-x64-musl": "12.17.0",
+    "@pnpm/exe.linux-arm64-musl": "12.17.0",
+    "@pnpm/exe.freebsd-x64": "12.17.0",
+    "@pnpm/exe.android-arm64": "12.17.0",
+    "@pnpm/exe.android-x64": "12.17.0"
   },
   "scripts": {
     "preinstall": "node install.js",