Repository navigation
pnpm update --global migrates global packages from <global-dir>/5 to <global-dir>/v11 but leaves hard links in <pnpm-home> #16420
Description
Last pnpm version that worked
12.7
pnpm version
12.8.1
Code to reproduce the issue
Run pnpm update --global on pnpm version 12.8 or 12.8.1, issue introduced in #15686
Expected behavior
Since, hard links are expected at <pnpm-home>/bin from v11; links at <pnpm-home> should be removed with this migration.
Actual behavior
With the merging of #15686 , pnpm update --global migrates global packages from <global-dir>/5 to <global-dir>/v11 but leaves hard links in <pnpm-home>.
Additional information
Node.js version
NA
Operating System
macOS
Contributing a fix
- I am working on a fix
Activity
zkochan commentedon Sep 30, 2026
Opened #16425 to fix migration cleanup in both pnpm v11 and v12. It identifies hard links by comparing them with the old packages' executable files, including Windows
.exepaths, and preserves unrelated files.This fixes cleanup when the old installation still exists. It cannot safely identify leftovers from an already completed migration after the old package metadata and executable files have been deleted.
Written by an agent (Codex, GPT-6).
fix(deps): update dependencias no-major (#23)
chore(deps): update pnpm to v12.9.0
chore(deps): update pnpm to v12.9.0
chore(deps): update pnpm to v12.9.0
chore(deps): update pnpm to v12.9.0
chore(deps): update pnpm to v12.9.0