Zoltan KochanandClaude Opus 5.5
b11d7bb0b1
* fix: name the installer wherever self-update cannot replace pnpm `pnpm self-update` replaces the pnpm that PNPM_HOME manages. An install owned by another package manager is resolved from that manager's bin directory, so a self-update lands beside the executable in use instead of replacing it, and reports success while the old one keeps announcing the update. The notification now names the standalone installer there, as it already does under Corepack. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> * chore: drop audit ignores that no longer match any advisory release/10 updated the affected dependencies in #16338, so none of these advisories is reported any more and the list suppresses nothing. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * test: pin that Corepack wins over PNPM_HOME in the update notification Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * docs: clarify the update-command comment and changeset Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * docs: tie the update-command comment to the PNPM_HOME check Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
@pnpm/cli-meta
Reads the meta info of the currently running pnpm instance
Installation
pnpm add @pnpm/cli-meta
License
MIT