Skip to main content

pnpm 12.18.0

Release Date: November 5, 2026

pnpm 12.18.0 landed on November 5, 2026 with four headline moves: platform variants for pnpr registries, per-skill approval of agent skills, pnpm store add for offline installs, and a repeat-install path that stops reading package.json for workspace projects that did not change.

📦 Platform Variants Reach Pack and Publish

Everything in this section needs a registry declared with serverType: pnpr.

  • One archive per variant. pnpm pack writes an archive for each entry of publishConfig.variants, named <name>-<version>~<tag>.tgz. --variant <target> packs just one, and --json reports the integrity and size of every archive it wrote.
  • Uploads before the publish request. pnpm publish sends every archive first, then the publish request that references them. A registry without serverType: pnpr is refused unless --no-variants is passed, which publishes only the any archive.
  • Split publish across jobs. --upload-variant <target> pushes one archive to the staging area and prints <target>=<integrity>; a later job publishes with --variant-integrity. In a recursive batch the values are prefixed with the package name.
  • Install picks the host fit. The lockfile records every variant, installs the one matching the host, skips an optional dependency when nothing fits, and fails a required one with the list of published platforms.
  • Platform tags in supportedArchitectures. Entries may carry floors and an ABI, such as linux-x64-manylinux_2_28, darwin-arm64-macos_14_0, linux-x64-napi8 or linux-x64-node127, plus non-Node targets like freebsd-x64. The older spellings still parse.
  • Identical republish is accepted. Rerunning pnpm publish for a version that is already live succeeds when the archives, provenance statement and dist-tag match. A mismatch fails with ERR_PNPM_PUBLISHED_RELEASE_DIFFERS and names the difference.

🤖 Agent Skills Get Real Names and Real Approvals

  • Links named after the skill. A skill shipped in @acme/kit at skills/auth/ now links as .claude/skills/auth instead of pnpm-@acme+kit-auth. The next install replaces the old links and records them in a # pnpm block of the directory's .gitignore.
  • Collisions link instead of failing. When two approved packages ship the same skill name, or the name is already taken, pnpm falls back to pnpm-<package>-<skill>.
  • Per-skill approval. pnpm approve asks which skills to link when a package ships several, stores the answer as a list, and asks once which agent directories to use, recording it under skills.dirs.
  • Nested category directories. Skills three levels below skills/, such as skills/engineering/implement/SKILL.md, are now linked.

⚡ Speed Surge

  • Fewer package.json reads. pnpm install, and pnpm run or pnpm exec with verifyDepsBeforeRun, skip projects whose files did not change. This holds with a pnpmfile, configDependencies, or sharedWorkspaceLockfile: false.
  • Recursive runs stop re-reading the workspace. In a 300-project workspace, pnpm -r exec true drops from 490 ms to 42 ms.
  • Leaner pnpr metadata. Package documents omit manifests of rarely picked versions and are fetched on demand. A 787-package resolution benchmark falls from 30.3 MB to 2.5 MB gzipped, cached under v12/metadata-pnpr.
  • Cheaper hardlinks. Install makes as few stat calls as 12.7.0 did when linking files out of the store.

🐛 Bug Bashes

  • Peer resolution. Deduplication no longer splits direct and transitive paths when an optional peer has no provider, dependencies stop binding to another project's peer variant when providers have nested peers, and pnpm peers check warns about unprovided required peers without failing strictPeerDependencies.
  • Frozen lockfiles. --frozen-lockfile accepts lockfiles that resolve a * dependency to a prerelease latest, ones written with excludeLinksFromLockfile plus linkWorkspacePackages and a catalog: entry, and ones with addMissingPeerTypes and an injected workspace package that has peers.
  • Offline installs. pnpm store add ./tarballs/*.tgz prepares the store so a later pnpm install --offline --frozen-lockfile can satisfy entries that pin those tarballs.
  • Link safety. pnpm link now refuses a package name that is not a valid npm name without writing it to package.json or pnpm-workspace.yaml, and a relative target resolves from the current directory.
  • Node.js ranges. A range such as >=26.13 in devEngines.runtime resolves to the newest stable release, and picks a prerelease only when no stable version matches.
  • Config from the environment. linkWorkspacePackages, injectWorkspacePackages, extendNodePath, frozenStore and optimisticRepeatInstall now read from PNPM_CONFIG_* variables.

Install with npm install -g [email protected], or switch the project pin through corepack and let the next install migrate the workspace.

Other Versions

We use cookies for ads and analytics.