pnpm 12.10.1 → 12.11.1

package/CHANGELOG.md

@@ -1,5 +1,143 @@
 # pnpm
 
+## 12.11.1
+
+This release fixes two ways `pnpm install` could fail, runs tools of any Rust release through `pnx`, and treats `registry.npmjs.com` as an alias of the npm registry.
+
+### Patch Changes
+
+- `pnpm install` no longer fails when `packageManager` pins the pnpm version that is already running and the registry does not publish that version. pnpm warns and continues. A registry mirror that has not synced a release no longer blocks the commands of a project pinned to it.
+
+- `pnpm install` no longer fails with `ERR_PNPM_CMD_SHIM_CHMOD` when `node_modules/.bin` holds a shim that another user created, if everyone can already execute it and it is not world-writable. This happens when several users share one checkout.
+
+- `enable-modules-dir=false` (`enableModulesDir: false` through the Node.js addon) fetches the registry packages the host can install into the store again, as pnpm v10 did, while still writing nothing under `node_modules`. The setting exists for a `node_modules` that something else mounts from the store, such as a FUSE daemon, and that consumer no longer has to download each package on first access. A plain `--lockfile-only` run still fetches nothing.
+
+- `pnpm pack` and `pnpm publish` no longer put `.npmignore` and `.gitignore` files in the tarball. A `files` entry that names one still ships it.
+
+- pnpm now treats `https://registry.npmjs.com/` as an alias of `https://registry.npmjs.org/`. Registry requests, credentials, and trusted publishing use the canonical hostname.
+
+- `pnx --package=rust@<channel> <tool>` runs a tool of that Rust release, for example `pnx --package=rust@nightly-2026-01-01 cargo build`. pnpm installs the release with the components and targets from `rust-toolchain.toml` and the target of each `--target` argument.
+
+- `pnpm install` now links agent skills for more coding agents. It detects the agent from `ANTIGRAVITY_AGENT`, `COPILOT_AGENT`, `COPILOT_CLI`, `CODEX_THREAD_ID`, `CODEX_SANDBOX`, `AI_AGENT`, and `CLAUDE_CODE` [pnpm/tasks#116](https://github.com/pnpm/tasks/issues/116).
+
+- When the registry rejects `pnpm stage publish`, the error message now starts with "Failed to stage package".
+
+## 12.11.0
+
+This release adds Rust toolchain management, links the agent skills that dependencies ship, adds the `permissions` setting, and keeps the colors of streamed script output.
+
+### Minor Changes
+
+- `pnpm install` now links the agent skills that direct dependencies ship under `skills/<name>/SKILL.md` into the project's agent skill directories, such as `.claude/skills`. A package's skills are linked only after you approve them with `pnpm approve`. The `skills.dirs` setting chooses the directories [pnpm/rfcs#35](https://github.com/pnpm/rfcs/pull/35).
+
+  Added the `permissions` setting, which records what each dependency may do. Its `build` capability works like `allowBuilds` and takes precedence over it. `pnpm approve-builds` writes to `permissions` when `pnpm-workspace.yaml` already has it, and to `allowBuilds` otherwise.
+
+  Added `pnpm permissions`, which lists the granted and denied permissions and the packages awaiting approval. `pnpm approve` reviews build scripts and agent skills in one prompt [pnpm/rfcs#36](https://github.com/pnpm/rfcs/pull/36).
+
+- pnpm now installs and runs Rust toolchains.
+
+  - With `cargo.enabled`, `pnpm install` installs the toolchain named in `rust-toolchain.toml`. pnpm verifies the release signature, stores the toolchain once per machine, and links it into `.pnpm/rust`. `pnpm run` and `pnpm exec` put its `cargo` and `rustc` on the `PATH`.
+  - `pnpm add -g rust@<channel>` installs a toolchain globally. The `cargo` and `rustc` commands run it outside projects that pin their own. `pnpm update -g`, `pnpm ls -g`, and `pnpm remove -g` manage it like any global package.
+  - In a project, `pnpm add rust@<channel>` pins the toolchain in `rust-toolchain.toml`.
+  - `pnpm shim add rust` adds project-aware shims for `cargo`, `rustc`, and the other Rust tools. In a project with a `rust-toolchain.toml`, they run the toolchain the file names and install it on first use. Elsewhere, the next command of the same name on `PATH` runs, such as rustup's.
+
+- `pnpm run` and `pnpm exec` now keep the colors of script output that they print under the project's name, such as with `--stream`. pnpm sets `FORCE_COLOR=1` for these scripts when its own output is in color, unless `FORCE_COLOR` is already set.
+
+  Script output is also rendered more cleanly:
+
+  - A line that a progress bar redraws with `\r` shows only its last state.
+  - Escape codes that move the cursor or clear the screen are dropped.
+  - Long colored lines are cut at the terminal width.
+  - `pnpm -r run` no longer garbles its live output when a script fails while other scripts are still running.
+
+### Patch Changes
+
+#### Installing packages
+
+- pnpm no longer panics with "unexpected error when polling the I/O driver" when it runs under QEMU user-mode emulation, such as a `linux/amd64` container on an Apple Silicon Mac [#16696](https://github.com/pnpm/pnpm/issues/16696).
+
+- `pnpm view`, `pnpm update`, and other commands that read registry metadata now work behind proxies that end a response by closing the connection without a TLS `close_notify` alert [#16704](https://github.com/pnpm/pnpm/issues/16704).
+
+- pnpm now switches to the version a project pins in `packageManager` or `devEngines.packageManager` even when `pnpm-workspace.yaml` has a setting the running pnpm cannot read, such as a `lockfile.includeResolutionSettings` section. If pnpm does not switch, it still reports that setting [#16675](https://github.com/pnpm/pnpm/issues/16675).
+
+- When the `pnpm` package has to download its native binary on first run, it now uses the registry and credentials from `.npmrc` and from the `npm_config_registry` and `pnpm_config_registry` environment variables. `COREPACK_NPM_REGISTRY` still takes precedence. A project `.npmrc` is not read when `COREPACK_INTEGRITY_KEYS` turns off the signature check [#16655](https://github.com/pnpm/pnpm/issues/16655).
+
+- `pnpm install` and `pnpm add --config` now apply `minimumReleaseAge` when they resolve a config dependency. A config dependency range resolves to the newest version that is old enough, so a later clean `pnpm install --frozen-lockfile` accepts the lockfile [#16660](https://github.com/pnpm/pnpm/issues/16660).
+
+- `pnpm remove` with `catalogPrune` no longer removes catalog entries that `pnpm-lock.yaml` still records for workspace projects missing from disk. Before, a following frozen install failed with `ERR_PNPM_LOCKFILE_CONFIG_MISMATCH` [#16679](https://github.com/pnpm/pnpm/issues/16679).
+
+- With `cargo.enabled`, `pnpm install` now writes the source replacement for vendored crates into `.pnpm/crates/config.toml` and includes it as optional from `.cargo/config.toml`. A checkout without `.pnpm` builds with plain Cargo [#16659](https://github.com/pnpm/pnpm/issues/16659).
+
+- With `nodeLinker.type` set to `loaded`, Node.js now stops with `ERR_PNPM_LOADER_UNSUPPORTED_NODE` when it preloads the store loader on a version the loader cannot serve. The supported versions are `^24.18.0 || >=26.2.0`. On other versions, CommonJS packages imported from ESM failed with `Cannot find module` on their first relative `require()`.
+
+- On Windows, `pnpm install` no longer fails with "The filename, directory name, or volume label syntax is incorrect" when a package contains a file whose name is invalid on Windows, such as `icon.svg?as=metadata.d.ts`. pnpm removes the invalid characters from the name and prints a warning that lists the renamed files.
+
+- On Windows, hoisting no longer fails intermittently with link errors when a junction is created or replaced concurrently [pnpm/tasks#53](https://github.com/pnpm/tasks/issues/53).
+
+#### Resolving dependencies
+
+- `pnpm install --no-optional` now installs the peer dependencies a project declares when `autoInstallPeers` is on. The lockfile marked such a peer `optional: true` when another dependency had it as an optional peer.
+
+- `pnpm install` and `pnpm dedupe` now link an optional peer to the workspace package that the workspace root depends on when the picked version matches it. They installed the registry package with the same name and version [#16706](https://github.com/pnpm/pnpm/issues/16706).
+
+- Removal overrides such as `"debug>supports-color": "-"` now also apply to an optional peer that a package declares only in `peerDependenciesMeta` [#16681](https://github.com/pnpm/pnpm/issues/16681).
+
+- `pnpm add` and other installs that re-resolve dependencies now keep the locked `devEngines.runtime` version while it still satisfies the declared range [#16764](https://github.com/pnpm/pnpm/issues/16764).
+
+- `pnpm audit --fix update` now updates only the dependencies whose locked version is vulnerable [#14928](https://github.com/pnpm/pnpm/issues/14928).
+
+- `pnpm outdated` and `pnpm update --interactive` now apply `overrides` before they look up the latest version. Before, a dependency overridden to an npm alias was compared with the latest version of the package the override replaces [#16719](https://github.com/pnpm/pnpm/issues/16719).
+
+#### Patched dependencies
+
+- Patches saved with CRLF line endings now apply, including a patch that creates or deletes a file. pnpm rejected the git headers of such a patch with `ERR_PNPM_INVALID_PATCH` and the message `invalid file mode: 100644` [#16641](https://github.com/pnpm/pnpm/issues/16641).
+
+- A patch that changes a file's mode, such as adding or removing the executable bit, now applies the new mode on Unix [pnpm/tasks#110](https://github.com/pnpm/tasks/issues/110).
+
+#### Injected dependencies and deploy
+
+- With `sharedWorkspaceLockfile: false`, an injected workspace package installed in the same run as its dependent now holds only the files its `files` field selects. The copy also held other files of the project, such as `tsconfig.json` [#16683](https://github.com/pnpm/pnpm/issues/16683).
+
+- A script listed in `syncInjectedDepsAfterScripts` no longer fails when it rewrites `package.json` while pnpm is copying its edits into the injected copies. The sync after the script now replaces a half-copied manifest.
+
+- `pnpm deploy` with a shared lockfile no longer fails with `ERR_PNPM_LOCKFILE_CONFIG_MISMATCH` for `settings.dedupeInjectedDeps` or `settings.dedupePeerDependents` when `lockfile.includeResolutionSettings` is enabled. The deployed lockfile now records both settings as `false`, the values the deploy installs with.
+
+- `pnpm deploy` now writes the dependencies in the deployed `package.json` sorted by name. It also sorts the `allowBuilds` entries in the deployed `pnpm-workspace.yaml`. Repeated deploys of the same lockfile now produce identical files [#16687](https://github.com/pnpm/pnpm/issues/16687).
+
+#### Packing and publishing
+
+- `pnpm pack` and `pnpm publish` now match `.npmignore` and `.gitignore` rules the way npm does. A negation such as `!lib/**` or `!lib/**/!(*.map)` re-includes files under a directory that an earlier `*` rule excluded [#16743](https://github.com/pnpm/pnpm/issues/16743).
+
+- `pnpm pack` and `pnpm publish` no longer always include root files that merely start with `README`, `LICENSE`, or `LICENCE`, such as `README_INTERNAL.md`. Only `README`, `LICENSE`, `LICENCE`, and `COPYING`, with or without an extension, ship regardless of `files` and `.npmignore`, as in npm [#16753](https://github.com/pnpm/pnpm/issues/16753).
+
+- `pnpm publish --provenance=false` and `--no-provenance` now turn off provenance under trusted publishing, so a package can be published from a self-hosted runner. Setting `provenance: false` in `pnpm-workspace.yaml` does the same [#16721](https://github.com/pnpm/pnpm/issues/16721).
+
+#### Speed and resource use
+
+- `pnpm install` hardlinks files from a group-writable or world-writable store again. pnpm copied every file from such a store into `node_modules` [#16677](https://github.com/pnpm/pnpm/issues/16677).
+
+- A repeat `pnpm install` no longer imports patched packages and packages with build scripts again when nothing changed. Their builds no longer run again either. This happened when `recursiveInstall` was `false` or the project had a `file:` dependency [#16705](https://github.com/pnpm/pnpm/issues/16705).
+
+- Verifying the lockfile against `trustPolicy` and `minimumReleaseAge` uses less memory. pnpm no longer keeps every published version's manifest of each checked package in memory until the install ends [#16656](https://github.com/pnpm/pnpm/issues/16656).
+
+- `pnpm rebuild <pkg>` and `pnpm rebuild --pending` no longer read the manifest of every installed package to find build scripts. Only the selected packages are inspected and built. On a large `node_modules` served lazily, such as over a network or FUSE mount, this turned a rebuild of a few packages into a fetch of every package.
+
+- `pnpm rebuild` no longer removes and recreates `node_modules` when the settings recorded in `node_modules/.modules.yaml` differ from the current configuration. The rebuild runs the build scripts against the installed packages as they are.
+
+- `pnpm store prune` now compacts the store's `index.db` after removing package entries, so the file shrinks again [#16717](https://github.com/pnpm/pnpm/issues/16717).
+
+#### Registry commands
+
+- `pnpm whoami`, `pnpm bugs`, `pnpm docs`, `pnpm repo`, `pnpm star`, `pnpm unstar`, and `pnpm stars` now honor the `--registry` option.
+
+- `--registry` now takes precedence over a scope's configured registry for scoped packages in `pnpm access`, `pnpm view`, `pnpm repo`, `pnpm star`, `pnpm unstar`, `pnpm owner`, `pnpm deprecate`, `pnpm undeprecate`, `pnpm unpublish`, `pnpm dist-tag`, `pnpm team`, and `pnpm stage`. Without `--registry`, `pnpm access` now sends a scoped package or scope to the registry configured for that scope.
+
+- Registry commands now keep the path of a registry URL such as `https://example.com/npm/` when they build request URLs. This applies to `pnpm access`, `pnpm owner`, `pnpm ping`, `pnpm search`, `pnpm star`, `pnpm stars`, `pnpm team`, `pnpm unstar`, and `pnpm whoami`.
+
+- `pnpm view` now honors the network retry settings.
+
+- `pnpm repo` now fetches the repository URLs of several packages in parallel.
+
 ## 12.10.1
 
 This release fixes `pnpm install` failures after an `overrides` change and on a filtered frozen install with `catalogPrune`. It also fixes several bugs in the experimental `nodeLinker.type: loaded`, which now keeps its generated files in `node_modules`.

package/bin/pnpm.mjs

@@ -17,12 +17,13 @@
 //
 // The download itself is `get-pnpm`, the package behind https://get.pnpm.io,
 // which already knows how to verify one; it travels in that same `dist/`
-// payload. What is left here is Corepack's environment, which it does not know:
-// where to download from, what credentials to use, and whose signature to trust.
+// payload. What is left here is what it does not know: where to download from,
+// what credentials to use, and whose signature to trust.
 import { Buffer } from 'node:buffer'
 import { spawnSync } from 'node:child_process'
 import console from 'node:console'
 import fs from 'node:fs'
+import net from 'node:net'
 import os from 'node:os'
 import path from 'node:path'
 import process from 'node:process'
@@ -78,13 +79,13 @@ async function nativeBinary () {
   const { downloadPnpmExecutable } = await import(GET_PNPM).catch((err) => {
     fail(`This copy of the pnpm package is missing the downloader it needs: ${err.message}`)
   })
+  const signature = signaturePolicy()
   try {
     await downloadPnpmExecutable({
       version,
-      registry: process.env.COREPACK_NPM_REGISTRY || DEFAULT_REGISTRY,
       destPath: DOWNLOADED_BINARY,
-      headers: registryHeaders(),
-      ...signaturePolicy(),
+      ...registryAccess({ readProjectNpmrc: signature.verifySignature !== false }),
+      ...signature,
     })
   } catch (err) {
     fail(`Could not download the pnpm ${version} binary: ${err.message}`)
@@ -93,22 +94,188 @@ async function nativeBinary () {
 }
 
 /**
- * Credentials for the registry, read the way Corepack reads its own. `get-pnpm`
- * keeps them on that registry's origin, so a download host it names never
- * receives them.
+ * The registry to download from, and the headers to send it. Corepack's
+ * `COREPACK_NPM_REGISTRY` wins. Otherwise npm's sources decide, highest first:
+ * the environment, the project `.npmrc`, the user `.npmrc`.
+ *
+ * The project `.npmrc` is read only with `readProjectNpmrc`, which the caller
+ * passes while the download is checked against npm's signature. The signature
+ * pins the bytes, so a repository picks only where they come from. Unchecked,
+ * it would pick the binary itself, which is kept next to this wrapper and run
+ * in every later project (GHSA-j2hc-m6cf-6jm8). `get-pnpm` keeps the headers on
+ * the registry's origin, so a download host it names never receives them.
  */
-function registryHeaders () {
+function registryAccess ({ readProjectNpmrc }) {
+  const corepackRegistry = process.env.COREPACK_NPM_REGISTRY
+  if (corepackRegistry) {
+    return { registry: corepackRegistry, headers: corepackHeaders() }
+  }
+  const npmrc = readUserNpmrc()
+  if (readProjectNpmrc) {
+    Object.assign(npmrc, readNpmrc(path.join(projectDir(), '.npmrc'), projectEntry))
+  }
+  const registry = npmrc['@pnpm:registry'] || settingFromEnv('registry') || npmrc.registry
+  if (!registry) {
+    return { registry: DEFAULT_REGISTRY, headers: corepackHeaders() }
+  }
+  return { registry, headers: npmrcHeaders(npmrc, registry) }
+}
+
+/** Credentials for Corepack's registry, read the way Corepack reads its own. */
+function corepackHeaders () {
   const { COREPACK_NPM_TOKEN, COREPACK_NPM_USERNAME, COREPACK_NPM_PASSWORD } = process.env
   if (COREPACK_NPM_TOKEN) {
     return { authorization: `Bearer ${COREPACK_NPM_TOKEN}` }
   }
   if (COREPACK_NPM_USERNAME && COREPACK_NPM_PASSWORD) {
-    const credentials = Buffer.from(`${COREPACK_NPM_USERNAME}:${COREPACK_NPM_PASSWORD}`, 'utf8')
-    return { authorization: `Basic ${credentials.toString('base64')}` }
+    return { authorization: `Basic ${base64(`${COREPACK_NPM_USERNAME}:${COREPACK_NPM_PASSWORD}`)}` }
   }
   return undefined
 }
 
+function settingFromEnv (key) {
+  const upper = key.toUpperCase()
+  const { env } = process
+  return env[`pnpm_config_${key}`] || env[`PNPM_CONFIG_${upper}`] ||
+    env[`npm_config_${key}`] || env[`NPM_CONFIG_${upper}`] || undefined
+}
+
+/** The user `.npmrc`, with `${VAR}` placeholders expanded. */
+function readUserNpmrc () {
+  return readNpmrc(
+    settingFromEnv('userconfig') || path.join(os.homedir(), '.npmrc'),
+    (key, value) => [expandEnv(key), expandEnv(value)]
+  )
+}
+
+/**
+ * A project `.npmrc` entry, which is not expanded. One with a `${VAR}`
+ * placeholder in a registry setting or a credential is dropped, as pnpm drops
+ * it: a repository must not route the user's environment to a registry.
+ */
+function projectEntry (key, value, file) {
+  if (!key.includes('${') && !value.includes('${')) {
+    return [key, value]
+  }
+  if (key.startsWith('//') || key === 'registry' || key.endsWith(':registry')) {
+    console.error(`Ignored ${key} from ${file}: a project .npmrc cannot use environment variables in registry settings or credentials.`)
+  }
+  return undefined
+}
+
+/** Where pnpm reads the project `.npmrc`: the workspace root, or else the current directory. */
+function projectDir () {
+  const cwd = process.cwd()
+  for (let dir = cwd; ; dir = path.dirname(dir)) {
+    if (fs.existsSync(path.join(dir, 'pnpm-workspace.yaml'))) {
+      return dir
+    }
+    if (path.dirname(dir) === dir) {
+      return cwd
+    }
+  }
+}
+
+/**
+ * The top-level settings of the `.npmrc` at `file`, each passed through
+ * `parseEntry`, which returns the `[key, value]` to keep or `undefined`.
+ */
+function readNpmrc (file, parseEntry) {
+  const settings = Object.create(null)
+  let text
+  try {
+    text = fs.readFileSync(file, 'utf8')
+  } catch (err) {
+    if (err.code !== 'ENOENT' && err.code !== 'EISDIR') {
+      console.error(`Could not read ${file}, so its settings are not used: ${err.message}`)
+    }
+    return settings
+  }
+  for (const rawLine of text.split(/\r?\n/)) {
+    const line = rawLine.trim()
+    // Settings under a `[section]` are not top-level ones.
+    if (line.startsWith('[')) {
+      break
+    }
+    const separator = line.indexOf('=')
+    if (separator === -1 || line.startsWith(';') || line.startsWith('#')) {
+      continue
+    }
+    const entry = parseEntry(line.slice(0, separator).trim(), unquote(line.slice(separator + 1).trim()), file)
+    if (entry != null) {
+      settings[entry[0]] = entry[1]
+    }
+  }
+  return settings
+}
+
+function unquote (value) {
+  const quoted = value.length >= 2 && (value[0] === '"' || value[0] === "'") && value.at(-1) === value[0]
+  return quoted ? value.slice(1, -1) : value
+}
+
+function expandEnv (value) {
+  return value.replace(/\$\{([^${}]+)\}/g, (_, name) => process.env[name] ?? '')
+}
+
+/**
+ * The credentials the `.npmrc` holds for `registry`, looked up as pnpm looks
+ * them up for an `@pnpm` package: the `@pnpm` scope's own credentials first,
+ * then the registry-wide ones. Each is the longest `//host[:port]/path/`
+ * prefix of the registry URL that has any, then the same without the port.
+ * They are sent only over HTTPS or to the local machine.
+ */
+function npmrcHeaders (npmrc, registry) {
+  const url = new URL(registry.endsWith('/') ? registry : `${registry}/`)
+  if (url.protocol !== 'https:' && !(url.protocol === 'http:' && isLoopback(url.hostname))) {
+    return undefined
+  }
+  const prefixes = []
+  for (const host of new Set([url.host, url.hostname])) {
+    for (let pathname = url.pathname; ; pathname = pathname.slice(0, pathname.lastIndexOf('/', pathname.length - 2) + 1)) {
+      prefixes.push(`//${host}${pathname}`)
+      if (pathname === '/') {
+        break
+      }
+    }
+  }
+  for (const scope of [':@pnpm', '']) {
+    for (const prefix of prefixes) {
+      const authorization = npmrcAuthorization(npmrc, `${prefix}${scope}`)
+      if (authorization != null) {
+        return { authorization }
+      }
+    }
+  }
+  return undefined
+}
+
+function isLoopback (hostname) {
+  return hostname === 'localhost' || hostname === '[::1]' ||
+    (net.isIPv4(hostname) && hostname.startsWith('127.'))
+}
+
+function npmrcAuthorization (npmrc, prefix) {
+  const token = npmrc[`${prefix}:_authToken`]
+  if (token) {
+    return `Bearer ${token}`
+  }
+  const auth = npmrc[`${prefix}:_auth`]
+  if (auth) {
+    return `Basic ${auth}`
+  }
+  const username = npmrc[`${prefix}:username`]
+  const password = npmrc[`${prefix}:_password`]
+  if (username && password) {
+    return `Basic ${base64(`${username}:${Buffer.from(password, 'base64').toString('utf8')}`)}`
+  }
+  return undefined
+}
+
+function base64 (text) {
+  return Buffer.from(text, 'utf8').toString('base64')
+}
+
 /**
  * Whose signature over the download to trust, following `COREPACK_INTEGRITY_KEYS`
  * exactly as Corepack does: npm's own keys when it is unset, the keys it names

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

@@ -1,9 +1,9 @@
 {
-  "lastValidatedTimestamp": 1791305376391,
+  "lastValidatedTimestamp": 1791546187431,
   "projects": {
     "/home/runner/_work/pnpm/pnpm/pnpm/npm/pnpm/temp-deploy": {
       "name": "pacquet",
-      "version": "12.10.1",
+      "version": "12.11.1",
       "hasModulesDir": true
     }
   },
@@ -46,7 +46,7 @@
         "@pnpm/tabtab": "^0.5.4",
         "@pnpm/tgz-fixtures": "0.0.0",
         "@reflink/reflink": "0.1.19",
-        "@rushstack/worker-pool": "0.7.29",
+        "@rushstack/worker-pool": "0.7.30",
         "@stylistic/eslint-plugin": "^5.10.0",
         "@tybys/wasm-util": "0.10.4",
         "@types/adm-zip": "^0.5.8",
@@ -88,7 +88,7 @@
         "@types/yarnpkg__lockfile": "^1.1.9",
         "@types/yauzl": "^3.4.0",
         "@types/zkochan__table": "npm:@types/table@6.3.2",
-        "@typescript-eslint/utils": "^8.71.0",
+        "@typescript-eslint/utils": "^8.71.1",
         "@typescript/native-preview": "7.0.0-dev.20260707.2",
         "@webcontainer/api": "^1.6.4",
         "@yarnpkg/core": "4.9.1",
@@ -170,7 +170,7 @@
         "jest-diff": "30.4.1",
         "js-yaml": "npm:@zkochan/js-yaml@0.0.11",
         "json5": "^2.2.3",
-        "keyv": "5.6.0",
+        "keyv": "6.1.0",
         "lcov-result-merger": "^6.0.0",
         "libnpmpublish": "^11.2.0",
         "load-json-file": "^7.0.1",
@@ -261,7 +261,7 @@
         "tree-kill": "^1.2.2",
         "ts-jest-resolver": "2.0.1",
         "typescript": "6.0.3",
-        "typescript-eslint": "^8.71.0",
+        "typescript-eslint": "^8.71.1",
         "uid-number": "0.0.6",
         "undici": "^7.29.1",
         "unified": "^11.0.5",

package/package.json

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