pnpm 12.18.0
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 packwrites an archive for each entry ofpublishConfig.variants, named<name>-<version>~<tag>.tgz.--variant <target>packs just one, and--jsonreports theintegrityandsizeof every archive it wrote. - Uploads before the publish request.
pnpm publishsends every archive first, then the publish request that references them. A registry withoutserverType: pnpris refused unless--no-variantsis passed, which publishes only theanyarchive. - 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 aslinux-x64-manylinux_2_28,darwin-arm64-macos_14_0,linux-x64-napi8orlinux-x64-node127, plus non-Node targets likefreebsd-x64. The older spellings still parse. - Identical republish is accepted. Rerunning
pnpm publishfor a version that is already live succeeds when the archives, provenance statement and dist-tag match. A mismatch fails withERR_PNPM_PUBLISHED_RELEASE_DIFFERSand names the difference.
🤖 Agent Skills Get Real Names and Real Approvals
- Links named after the skill. A skill shipped in
@acme/kitatskills/auth/now links as.claude/skills/authinstead ofpnpm-@acme+kit-auth. The next install replaces the old links and records them in a# pnpmblock 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 approveasks 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 underskills.dirs. - Nested category directories. Skills three levels below
skills/, such asskills/engineering/implement/SKILL.md, are now linked.
⚡ Speed Surge
- Fewer
package.jsonreads.pnpm install, andpnpm runorpnpm execwithverifyDepsBeforeRun, skip projects whose files did not change. This holds with a pnpmfile,configDependencies, orsharedWorkspaceLockfile: false. - Recursive runs stop re-reading the workspace. In a 300-project workspace,
pnpm -r exec truedrops 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
statcalls 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 checkwarns about unprovided required peers without failingstrictPeerDependencies. - Frozen lockfiles.
--frozen-lockfileaccepts lockfiles that resolve a*dependency to a prereleaselatest, ones written withexcludeLinksFromLockfilepluslinkWorkspacePackagesand acatalog:entry, and ones withaddMissingPeerTypesand an injected workspace package that has peers. - Offline installs.
pnpm store add ./tarballs/*.tgzprepares the store so a laterpnpm install --offline --frozen-lockfilecan satisfy entries that pin those tarballs. - Link safety.
pnpm linknow refuses a package name that is not a valid npm name without writing it topackage.jsonorpnpm-workspace.yaml, and a relative target resolves from the current directory. - Node.js ranges. A range such as
>=26.13indevEngines.runtimeresolves to the newest stable release, and picks a prerelease only when no stable version matches. - Config from the environment.
linkWorkspacePackages,injectWorkspacePackages,extendNodePath,frozenStoreandoptimisticRepeatInstallnow read fromPNPM_CONFIG_*variables.
Install with npm install -g [email protected], or switch the project pin through corepack and let the next install migrate the workspace.