Repository navigation
chore(deps): update pnpm to v12 - #361
Merged
Merged
Conversation
renovate
Bot
force-pushed
the
renovate/pnpm-12.x
branch
15 times, most recently
from
October 22, 2026 23:57
a14c447 to
04a7d93
Compare
renovate
Bot
force-pushed
the
renovate/pnpm-12.x
branch
10 times, most recently
from
October 30, 2026 19:24
1c0bc1a to
9bc19dd
Compare
renovate
Bot
force-pushed
the
renovate/pnpm-12.x
branch
4 times, most recently
from
November 3, 2026 12:42
baee98e to
e51e708
Compare
renovate
Bot
force-pushed
the
renovate/pnpm-12.x
branch
8 times, most recently
from
November 10, 2026 23:24
bfef8cc to
3e47193
Compare
renovate
Bot
force-pushed
the
renovate/pnpm-12.x
branch
10 times, most recently
from
November 17, 2026 04:44
3caf0c1 to
08f74fd
Compare
renovate
Bot
force-pushed
the
renovate/pnpm-12.x
branch
from
November 17, 2026 19:12
08f74fd to
e6e4099
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Note
This PR body was truncated due to platform limits.
This PR contains the following updates:
11.28.11→12.19.0Release Notes
pnpm/pnpm (pnpm)
v12.19.0: pnpm 12.19Compare Source
pnpm 12.19.0 adds
pnpm fund, lets theloadednode linker handle packages that need a build, and adds theprojectScopedOptionalPeerssetting and an experimental JSON lockfile format. It also includes a security fix: an offline install error no longer prints registry credentials. pnpm now checks theenginesand platform fields of every workspace project, and many hoisted-linker and frozen-lockfile bugs are fixed.Minor Changes
Added
pnpm fund, which lists the funding URLs declared by the installed dependencies in the same treenpm fundprints. Use--jsonfor thenpm fund --jsonreport and--recursiveor--filterto report on workspace projects.pnpm fund <pkg>opens the funding URL of an installed package, and--whichpicks one when it lists several #7354.With
nodeLinker.type: loaded, packages that need a build no longer have to be listed innodeLinker.excluded. A package with a matching side-effects cache entry loads from the store. If side-effects cache reads and writes are enabled, pnpm builds an approved package once, saves the result to the side-effects cache, and then loads it from the store. This includes a build that changes no files in its package, so its script does not run again in other projects that use the same store. List a package insideEffectsCache.excludeif its build must run in every project, such as a git hook installer. pnpm materializes other cache misses, packages with native.nodeaddons, and their dependencies automatically.pnpm also scans JavaScript sources for filesystem imports and for
__dirnameorimport.meta, and materializes matching packages. The scan does not detect computed imports. List such packages innodeLinker.excluded.Added the
projectScopedOptionalPeerssetting. When it istrue, a project gets a missing optional peer dependency only if the project's own dependencies install a version of it. Another workspace project's dependencies, such as itsdevDependencies, no longer supply one.dedupePeerDependentskeeps deduplicating everything else #16666.Added the experimental
lockfile.format: v13setting. With it, pnpm writespnpm-lock.yamlin a JSON-like syntax, indented with tabs, with a trailing comma after every entry. The file is still valid YAML. The file has onepackagesentry per package version in place of thepackagesandsnapshotssections, and each entry records the versions of its peer dependencies as its properties. Updating a peer dependency then changes only the lines that record its version. pnpm reads lockfiles in both formats whatever the setting is.pnpm store addnow accepts directories of tarballs, such aspnpm store add ./tarballs, and adds every.tgz,.tar.gz, and.tarfile inside them recursively.pnpm store addis now faster when it adds many packages or local tarballs #17875.With
supportedArchitecturesset,pnpm installandpnpm fetchalso store, without linking them, the dependencies of the archives kept for the other listed platforms. A platform added to the setting gets its archives and their dependencies on the next install. Optional dependencies a listed platform cannot run are not stored, and one that fails to download is skipped. Dependencies from git repositories are not stored for other platforms.When
supportedArchitecturesnames exactly one platform and notcurrent, pnpm links that platform's variant of a package published with platform variants, together with that variant's dependencies. This holds for the list form and for theos,cpu, andlibcform. A variant whose floor or ABI the listed platform does not state is not linked for it: pnpm links another variant that fits, or the version's own archive. Changing the setting, or the platform of the host, such as anode_modulesmounted into a musl container or a Node.js with another ABI, relinks the package on the next install, even from a frozen lockfile.pnpm now provides a prebuilt binary for NetBSD 10 on x64 #17803.
Patch Changes
Security
Installs that failed or hung
pnpm install,pnpm ci, andpnpm install-testoutside a workspace now fail withERR_PNPM_NO_PKG_MANIFESTwhen the directory has nopackage.json,package.json5, orpackage.yaml. They no longer create apackage.json, a lockfile, andnode_modulesthere #17727.Fixed
pnpm installhanging when a concurrent tarball download or manifest read is cancelled while other tasks are waiting on the same archive.Running a global command such as
nodein a project that pins its version no longer hangs while pnpm installs that version. The hang kept starting new processes until the machine ran out of memory.A global command such as
nodenow runs the version a project pins whenPNPM_CONFIG_LOCKFILE_DIR,PNPM_CONFIG_VIRTUAL_STORE_ONLY, orPNPM_CONFIG_SYMLINKis set in the environment. Before, the dispatch failed with "the installed node executable is not under" the store.pnpm installnow fetches fresh metadata for a package when a version allowed byminimumReleaseAgeExcludeis missing from the cached metadata. Before, it could fail withERR_PNPM_NO_MATCHING_VERSIONwithout contacting the registry #17723.A
${VAR}placeholder in a registry URL inpnpm-workspace.yamlor the project.npmrcnow fails the command. pnpm does not expand environment variables in these files. Before, pnpm ignored such a URL and resolved packages from another registry, such as npmjs.org. pnpm now warns when it ignores a placeholder in a proxy,pnprServer, oruserAgentsetting inpnpm-workspace.yaml#17762.Fixed local package installs failing while a workspace lockfile is being written.
pnpm self-updateand switching to thepackageManagerversion now work behind a proxy that ends a response by closing the TLS connection without aclose_notifyalert. The registry signature check failed there withERR_PNPM_PNPM_ENGINE_IDENTITY_UNVERIFIABLE#17763.A package tarball that keeps failing to download now fails the install after
fetchRetriesretries. pnpm used to download it again with a second full set of retries, which doubled the wait. The error now names the actual download failure.When the native binary of the pnpm version a project pins fails to download, pnpm now reports the download error. It used to report only that no native binary was found for the host.
POSIX bin shims and the
pnpm,pn,pnpx, andpnxlaunchers now run inside a Nix build on macOS with the sandbox enabled. Installing again replaces the shims already innode_modules#17750.Fixed pnpm leaving process pipes open after it exits on macOS pnpm/tasks#229.
Engines and platform checks
pnpm install,pnpm add,pnpm update, andpnpm removenow check theengines,os,cpu, andlibcfields of every workspace project, including the workspace root.pnpm run -randpnpm exec -rcheck them before running anything. An incompatibleengines.pnpmfails the command. An incompatibleengines.nodeprints a warning, or fails the command withengineStrictenabled. An unsupported platform prints a warning. A project that downloads its own Node.js throughdevEngines.runtimeis checked against that Node.js #17751 pnpm/tasks#281 pnpm/tasks#299.Fixed missing warnings when a required dependency does not support the current Node.js version.
An optional dependency that declares no
os,cpu, orlibcfield is no longer skipped because its name contains only an operating system word, such asget-windowson macOS. pnpm now infers its platform from the name only when the name also has a cpu or libc token, such as-win32-x64#17774.Peer dependencies
With
dedupePeerDependents: false, a missing optional peer is no longer resolved from a version that only another workspace project depends on. The workspace root's dependencies still count ifresolvePeersFromWorkspaceRootistrue. Before, a tool in one project'sdevDependencies, such aswebpack-cli, could become an optional peer of another project's production dependencies #16666.pnpm installno longer gives a project an optional peer dependency that it skipped because a required peer would conflict with the project's dependencies. Before,dedupePeerDependentsmerged the project's copy of the package that declares the peer with another project's copy that resolves it #17781.pnpm installno longer fills in a missing optional peer dependency if a required peer it brings in conflicts with a version the project depends on. Before, such a peer was installed along with it and reported as unmet #17718.pnpm install --filterin a sparse checkout now counts the dependencies of workspace projects that are missing from disk when it resolves peer dependencies and marks packages as optional. The lockfile it writes no longer differs from a full checkout in those entries #17791.Frozen lockfile and workspace links
pnpm install --frozen-lockfilenow succeeds when a workspace project recorded inpnpm-lock.yamlhas an empty directory, such as a git submodule that was not checked out #17712.pnpm install --frozen-lockfilenow fails withERR_PNPM_OUTDATED_LOCKFILEwhen a workspace package linked through a plain semver range, such as^7.9.5, has changed to a version outside that range #17806.pnpm install --frozen-lockfileandverifyDepsBeforeRunnow accept aworkspace:dependency on a project whose version is not valid semver, such asworkspace:1on a project at version1. Before, they reported the lockfile thatpnpm installhad just written as out of date.pnpm install --frozen-lockfilenow accepts a lockfile when an injected workspace package declares afile:orlink:dependency with backslashes, such asfile:..\vendor, or with a slash after the protocol, such asfile:/./vendor. Before, the install reported the lockfile as out of date right afterpnpm installhad written it #17720.When a package injected through a path, such as
file:../libor../lib, gives one of its dependencies acatalog:specifier,pnpm install --frozen-lockfilenow reports the lockfile as outdated. For a bare path such as../lib,pnpm installnow also fails the way a fresh resolution does. Before, these installs accepted the existing lockfile #17722.Dependencies declared as
workspace:entries in catalogs now remain in the lockfile whenexcludeLinksFromLockfileis enabled. Frozen installs can restore these links afternode_modulesis removed pnpm/tasks#260.With
dedupeDirectDeps,pnpm installnow compareslink:dependencies by the directory they point at. A project'slink:dependency is removed when the workspace root links the same directory under a different path. It is kept when the root'slink:dependency has the same text but points at another directory. pnpm reports a dependency the root provides as removed only once, when it removes the project's link. The summary shows the package version of a removedlink:dependency pnpm/tasks#293.Hoisted node linker and custom modulesDir
With
nodeLinker: hoisted, a package that runs a lifecycle script or has a patch is now cloned or copied intonode_modules, as with the isolated linker. A build that rewrites one of its files no longer changes the store copy shared with other projects.With
nodeLinker: hoisted, pnpm no longer deletes a directory outsidenode_moduleswhen it removes a package whose scope directory is a symlink.With
nodeLinker: hoisted,pnpm install --filterin a sparse checkout now drops previously installed workspace projects that are missing from disk from the hoistednode_modulestree. It no longer recreatesnode_modulesinside a missing project's directory. Packages that only the missing project used are also removed from the rootnode_modules.With
nodeLinker: hoistedanddedupeDirectDeps,pnpm installnow removes a project'slink:dependency that the workspace root provides, and reports eachlink:dependency it removes. Removing the last scopedlink:dependency of a scope also removes the empty@scopedirectory.With
nodeLinker: hoistedand a custommodulesDir, pnpm now installs a workspace project's dependencies that cannot be hoisted to the root into the project'smodulesDir. The next install that relinks the project removes the copies that earlier installs left in itsnode_modules. A later install restores the project'smodulesDirwhen it was removed. Package directories that pnpm did not install are now also moved to.ignoredin a custommodulesDir.Fixed installs in a workspace whose
modulesDiris an absolute path, including one that goes through a symlink such as/tmpon macOS, or a path that starts with... Dependencies of workspace projects no longer end up outside the workspace, and the root project's dependencies,link:dependencies, and commands are linked into the configured directory.pnpm bin,pnpm root,pnpm run,pnpm exec, andpnpm versionnow use that directory too pnpm/tasks#285.Store and builds
Concurrent installs into a global virtual store no longer wait on each other. A package that needs a build is built in a private directory and moved into the store once its build has finished, so another project never links a half-built package. An install with
--ignore-scriptslinks the packages it does not build from their own store directories, andpnpm store pruneremoves the build directories of installs that were interrupted #15568.Packages that an older pnpm version added to the store now run their install scripts. Before, pnpm could skip those scripts and hardlink the package's files to the store.
pnpm installnow keeps patches to bundled dependencies when it restores a package from the side-effects cache, including files a patch adds #17734.Local installs on macOS now keep cached clones separate from the global virtual store.
pnpm store pruneremoves this cache, so unused cached packages no longer accumulate #17907.pnpm store prunenow stops if a dependency link cannot be read. This keeps installed packages from being removed after an incomplete scan.A repeat
pnpm installnow runs a full install when theruntimeOnFailsetting changes. Before, it printed "Already up to date" and did not install the runtime a project declares indevEngines.runtimepnpm/tasks#303.The sync of an injected workspace dependency now copies a file whose source has reached the filesystem's limit on hard links.
pnpm patch-commitnow copies a file into its scratch directory when the filesystem refuses to hard link it, unless the path is missing or already occupied pnpm/tasks#283.Speed
pnpm installis faster when it clones files from the store, which it does by default on macOS. On a Mac with endpoint security software, a cold install of a project with about 1,350 packages took 29% less time pnpm/tasks#280.pnpm installunpacks packages that contain many files faster. Unpackingtypescripttook 30% less time in our measurements pnpm/tasks#288.Resolving against a registry that sends
Cache-Control: no-cache, such as Azure Artifacts, is fast again when the lockfile already decides the version. pnpm reads the cached metadata for a pinned version, or for a range the lockfile version is proven to win, without a registry request #17758.POSIX bin shims start fewer processes. Running a dependency's bin through its shim from Git Bash on Windows starts 7 processes where it started 15. Installing again replaces the shims already in
node_modules.Windows
pnpm now installs dependencies and runs lifecycle scripts from projects on mapped Windows network drives. When a network share refuses the links in
node_modules, the error now suggests settingnodeLinker: hoistedor moving the project to a local drive #17747.packageImportMethod: autonow tries hardlinking before cloning, as it does on Linux. Installs from a warm store on a Dev Drive are faster. An install no longer fails when the store refuses a hardlink with an access-denied error, and pnpm tries cloning or copying the file next #17809.pnpm runandpnpm setupno longer clear the visible terminal when a project path contains non-ASCII characters.A failed attempt to create a directory junction in
node_modulesno longer leaves a.pnpm-junction-*directory behind.pnpmstarts faster. It loads system libraries such asuser32.dllandshell32.dllthe first time a command uses them, sopnpm --versionloads 11 libraries where it loaded 25.pnpm deploy
pnpm deploynow runs the build scripts of a workspace project that it installs as afile:dependency, without a machine-specificallowBuildskey. AnallowBuildsentry that denies the project still applies #17740.pnpm deployno longer fails when the deployed project depends on a workspace package that setspublishConfig.directory. pnpm installs that package from its publish directory and runs its build scripts #17771.pnpm deploywithout a shared workspace lockfile now resolves a relativeworkspace:path, such asworkspace:../lib, from the source project's directory. It used to be resolved from the deploy target and fail #17804.pnpm deploy --offline --trust-lockfilenow reuses dependencies pinned in the source lockfile from a populated store when registry metadata is unavailable. This works with per-project lockfiles,--legacy, and npm aliases #17888.Other commands and settings
pnpm dist-tagandpnpm unpublishnow offer browser-based authentication when the account's two-factor authentication uses a security key. Before, they asked for a one-time password in that case #17832.pnpm publishwith provenance now downloads Sigstore's current signing configuration before signing. A failed or slow download is retried with the same retry policy and deadline as the signing requests.pnpm packandpnpm publishnow apply the first rule of a.npmignoreor.gitignorethat starts with a UTF-8 BOM.pnpm outdatednow checks dependencies when the project has no lockfile, for example withlockfile: false. TheCurrentcolumn shows the installed version, or the lowest version allowed by the declared range if the dependency is not installed #17811.pnpm self-updatenow updates the project'sengines.pnpmrange along with its pnpm pin, keeping the^or~operator #17732.On Linux and macOS,
pnpm runno longer sometimes reports a lifecycle failure afterCtrl+Cinterrupts a script.Config dependencies use the declared registry
serverTypewhen recording and installing packages pnpm/tasks#236.Relative directory selectors set on
config.filterorconfig.filterProdby anupdateConfighook now resolve from the workspace root even when--diris passed orpnpmruns from a subdirectory #17906.Commands that add settings to
pnpm-workspace.yamlnow fail with an error if the file contains onlynull, and leave the file unchanged. Before, they wrote invalid YAML.Shell tab-completion now completes directory and file paths for path options such as
-C,--dir,--prefix,--store-dir, and--env-file. Before, options without a fixed list of values offered command names #17884.Platinum Sponsors
Gold Sponsors
v12.18.0: pnpm 12.18Compare Source
pnpm 12.18.0 packs, publishes, and installs packages with platform variants on pnpr registries. It also adds per-skill approval of agent skills and
pnpm store addfor offline installs from downloaded tarballs. Repeat installs andverifyDepsBeforeRunno longer read thepackage.jsonof unchanged workspace projects. The release fixes several peer dependency resolution bugs too.Minor Changes
Agent skills
pnpm now names the link to a dependency's agent skill after the skill alone. A skill that the
@acme/kitpackage ships inskills/auth/is linked as.claude/skills/auth, not.claude/skills/pnpm-@acme+kit-auth. The next install replaces links with the old names. pnpm lists the linked skills in a# pnpmblock of each agent skill directory's.gitignore#17455.When two approved packages ship a skill of the same name, or the name is already taken in an agent skill directory, pnpm links the skill as
pnpm-<package>-<skill>. Before, the install failed.pnpm approvenow asks which agent skills to link when a package ships more than one. pnpm records the chosen skills as a list, such aspermissions.<pkg>.skills: [guide, migrate], and does not offer the other skills for approval again. The first time a project approves a skill,pnpm approvealso asks which agent directories to link skills into, and records the answer underskills.dirs.pnpm links agent skills nested in category directories, such as
skills/engineering/implement/SKILL.md, up to three levels belowskills/. Before, it linked only the skills directly underskills/.Platform variants
These features need a registry declared with
serverType: pnpr.pnpm packpacks one archive per entry ofpublishConfig.variants, each platform variant as<name>-<version>~<tag>.tgz.pnpm pack --variant <target>packs only the archive whose entry lists that target.pnpm pack --jsonprints theintegrityandsizeof every archive it writes.pnpm publishpublishes a package'spublishConfig.variants. pnpm uploads every archive before the publish request that references them. Publishing variants to any other registry is refused unless--no-variantsis given, which publishes only the archive that targetsany.pnpm publish --upload-variant <target>uploads the archive of onepublishConfig.variantsentry to the registry's staging area and prints<target>=<integrity>.pnpm publish --variant-integrity <target>=<integrity>then publishes the version from archives that other jobs uploaded. With--recursive, each value names its package as<name>~<target>=<integrity>.pnpm publish -r --batchnow uploads each package archive on its own request and skips archives the registry already holds, so the batch request no longer grows with the archives it publishes. A batch of more than 256 packages still carries every archive inline. Packages withpublishConfig.variantscan be published in a batch. A batch with variants that would reference more than 256 archives on one registry fails withERR_PNPM_BATCH_PUBLISH_TOO_MANY_ARCHIVESpnpm/tasks#244.pnpm publish --provenancesigns one statement that names every archive of a version withpublishConfig.variants. A platform variant's archive is named by the version's package URL with avariantqualifier.Rerunning
pnpm publishafter the version was already published now succeeds when the published version is the same release. pnpm compares the archives, the provenance statement when the rerun signs one, and the dist-tag. When the published version differs, the publish fails withERR_PNPM_PUBLISHED_RELEASE_DIFFERS, which names what differs.pnpm installs the platform variant of a package that fits the host, or the package's own archive when none does. The lockfile records every variant. A version published with variants only, and no archive for other hosts, installs on a host one of the variants fits. On any other host, an optional dependency is skipped, and any other dependency fails with an error that lists the platforms the version is published for.
supportedArchitecturesplatform lists accept platform tags, the same tagspublishConfig.variantsentries name. An entry can state floors and an ABI, such aslinux-x64-manylinux_2_28,darwin-arm64-macos_14_0,linux-x64-napi8orlinux-x64-node127, and any Node.js OS and CPU, such asfreebsd-x64. The spellings accepted before still work.With
supportedArchitecturesset, pnpm also fetches into the store the variants that the other listed platforms need, when it downloads a package with platform variants.pnpr registries
pnpm downloads less metadata from a registry declared with
serverType: pnpr. A large package document leaves out the manifests of rarely picked versions, and pnpm fetches one only when it picks that version. In a benchmark that resolves 787 packages, the package documents shrank from 30.3 MB to 2.5 MB gzipped. pnpm caches these documents inv12/metadata-pnpr, and thepnpm cachecommands cover them.pnpm warns when a registry that is not declared
serverType: pnprturns out to be pnpr. For a registry declaredserverType: pnpr, aminimumReleaseAgelonger than 30 days fails withERR_PNPM_UNSUPPORTED_MINIMUM_RELEASE_AGE.pnpm publishsends release notes to registries declared withserverType: pnpr. A package's notes are the section for its version inCHANGELOG.md, or the notes thatpnpm version -rcomposed from change intents.--release-notes <file>gives the notes from a file, and--no-release-notessends none.--publication-namenames a release published with--batch.In a workspace that uses pnpm's versioning,
pnpm version -r --release-notes <file>puts a summary above the composed notes of the release.pnpm view <pkg>@<version> releaseNotes,pnpm outdated --notes, andpnpm update --interactiveshow the release notes from these registries.Store and hooks
pnpm store addnow prepares the store for offline installs from package tarballs downloaded some other way. Afterpnpm store add ./tarballs/*.tgz,pnpm install --offline --frozen-lockfileinstalls each registry package whose lockfile entry pins one of those tarballs #2978.Custom pnpmfile fetchers can use
fetchers.gitHostedTarball,fetchers.git, andfetchers.binarypnpm/tasks#191.Patch Changes
Installing packages
Running
nodeorpnpm installin a project that pins a Node.js version pnpm has not downloaded yet no longer hangs when aglobalPnpmfileis configured #17530.pnpm installwithenableGlobalVirtualStoreno longer fails on Windows for a dependency from a named registry, such asgh:ornpmjs:#17665.Concurrent installs that share a global virtual store no longer fail with
ERR_PNPM_CMD_SHIM_SYMLINK_BINwhen they link the same executable at the same time #17587.pnpm installandpnpm cinow succeed when dependency skills are approved but no agent skill directory exists. The skills stay unlinked until a directory exists #17574.Commands run from a workspace package now use the same default store as the workspace root. Before,
pnpm addin a package could fail withERR_PNPM_UNEXPECTED_STOREwhen the workspace root was its own mount point and the home store was on another volume, as in a sandbox or a container.A workspace installed with the old behavior may need one
pnpm install --forcefrom the workspace root.pnpm deploynow keeps a symlink in the project whose target is missing from the source, such as a link into anode_modulesdirectory that was removed after the build. Deploy used to drop such a link silently #17571.pnpm installnow links the runtime that an earlierpnpm install --no-runtimeskipped, andpnpm install --no-runtimeremoves a runtime that an earlier install linked #17542.With
enableGlobalVirtualStore,pnpm installagain runs a dependency's build scripts in a project whose global virtual store slot another project already built, unless the side-effects cache has build output to restore for it. A build that writes only outside its own package, such as a git hook installer, now takes effect in every project #17526.Commands of a package whose
binpaths contain excess parent directory segments, such as../dist/cli.js, are no longer missing. Such paths now resolve inside the package #17586.Generated POSIX shell shims now quote their paths, so shell special characters in a path stay literal.
Lockfile and local paths
Packages from the default registry keep plain lockfile keys, even when a prefix such as
npmjspoints at the registry set asregistry. A dependency written with such a prefix shares the plain entry of the same package. The next install rewrites keys that earlier versions qualified this way #17575.pnpm install --frozen-lockfile,pnpm approve-builds, andpnpm rebuildnow accept a lockfile that resolves a*dependency to a prereleaselatestversion. pnpm wrote such a lockfile and then reported it as outdated #17594.pnpm install --frozen-lockfilenow accepts a lockfile written withexcludeLinksFromLockfileandlinkWorkspacePackageson, when a project depends on a workspace package through acatalog:entry. It used to fail withERR_PNPM_OUTDATED_LOCKFILE.pnpm install --frozen-lockfileno longer rejects a freshly generated lockfile whenaddMissingPeerTypesis enabled and an injected workspace package has peer dependencies #17668.Relative local paths in root
overridesnow resolve from the workspace root when each project has its own lockfile #17691.Installing a local directory dependency no longer fails when another project's install is writing a lockfile in that directory.
Relative local paths in root catalogs now resolve for dependencies and peers #17690.
pnpm installnow resolves auto-installed relativeworkspace:andfile:peers from the directory of the package that declares them #17676, #17689.pnpm dedupe --checkleavespnpm-lock.yamluntouched while it looks for deduplication changes. IfconfigDependencieschanged since the last install, the check keeps the lockfile they sync, aspnpm installdoes #17628.pnpm dedupe --checkno longer fails when the only difference is the integrity of a locked version that the registry now reports with a stronger algorithm, such as asha512integrity replacing thesha1shasum it reported when the lockfile was written #17692.Peer dependencies
Peer deduplication no longer gives a project different copies of a dependency across direct and transitive paths when an optional peer has no provider #17666.
Dependencies no longer bind to another project's peer variant when the provider has nested peers, including providers that finish resolving later #17593.
Re-resolving a lockfile no longer preserves optional peer bindings from other projects when no provider is in scope #17592.
pnpm peers checkwarns when a required peer is resolved without a provider declared by the project or its dependency ancestors, withautoInstallPeers: falseanddedupePeerDependents: true. These warnings do not change the command's exit code or causestrictPeerDependenciesfailures.Speed and memory
pnpm install, andpnpm runandpnpm execwithverifyDepsBeforeRun, no longer read thepackage.jsonof workspace projects whose files did not change since the last install. This also holds with a pnpmfile,configDependencies, orsharedWorkspaceLockfile: false. In an up-to-date workspace withsharedWorkspaceLockfile: false,pnpm installno longer runs the install of each project pnpm/tasks#256.A recursive
pnpm runorpnpm execwithverifyDepsBeforeRunset no longer reads everypackage.jsonin the workspace once per project whensharedWorkspaceLockfileisfalse. In a 300-project workspace,pnpm -r exec truewent from 490 ms to 42 ms pnpm/tasks#256.pnpm installmakes fewerstatcalls when it hardlinks files from the store, as few as 12.7.0 made #17543.Picking versions from registry metadata uses less temporary memory.
verifyDepsBeforeRun and repeat installs
With
verifyDepsBeforeRun,pnpm runandpnpm execnow report dependencies as out of date after a dependency is added to thepackage.jsonof a local directory dependency, such as"lib": "file:../lib". Before, the command ran without the new dependency installed.verifyDepsBeforeRunno longer reports afile:directory dependency as out of date after an edit topackage.jsonthat leaves its dependencies unchanged #17697.verifyDepsBeforeRunno longer reports dependencies as out of sync when only theversionfield of a single-project repository changed #17560. The same holds for a workspace project that no dependency can resolve to. A script run after such a change no longer starts an install first.A repeat
pnpm installnow rewrites the bin shims afterextendNodePathchanges. Before, it reported "Already up to date" and the shims kept theNODE_PATHof the previous setting.Adding and updating dependencies
pnpm add <pkg>without a version now saves the range that the other workspace projects declare for the package, or the one a matching override sets. Acatalog:reference still comes first, and thetagsetting is used only when none of these exists pnpm/tasks#191.pnpm updatewith only negated selectors, such aspnpm update '!foo', now leaves the dependencies listed inupdate.ignoreDepsunchanged. Negatedcrate:andpypi:selectors, such as!crate:sha2, now exclude that dependency and update the rest pnpm/tasks#243.pnpm update --latestkeeps three kinds of Cargo dependencies where they are, unless the crate is named on the command line. Before, it moved each one to the newest release and left a workspace that did not build.tower-0-4 = { package = "tower", version = "0.4" }, stays within its requirement if the workspace also declares the crate under its own name.[patch.crates-io]keeps its version, with a warning.pnpm update crate:foo@1, moves it back.Other new major versions are still selected and may need code changes.
pnpm updatenow keeps a Cargo dependency at its current version, with a warning, if the new version lacks a feature the workspace enables on it. If the crate is named on the command line, as inpnpm update --latest crate:sha2, the update fails with an error that names the missing features.pnpm updatenow keeps the operator of every existing Cargo requirement, so~1.0.0is updated to~1.1.0, and an exact=requirement stays exact unless the selector gives a range, such ascrate:foo@^2. ThesavePrefixandsaveExactsettings apply only to new Cargo dependencies. Saved Cargo requirements omit build metadata.pnpm updatenow updates a Cargo dependency whose inline table spans several lines, such as one with a multi-linefeaturesarray. It failed with "its Cargo.toml dependency declaration is not a string or single-line inline table".pnpm updateno longer applies thesavePrefixandsaveExactsettings to Python requirements. AsavePrefixsuch as^madepnpm updatefail in a project with Python dependencies.pnpm updatenow keeps the precision of a~=requirement, so~=1.0is updated to~=1.5and still allows any 1.x release. With--latest, a==1.*requirement is updated to==2.*.Store
pnpm store prunenow keeps packages linked from a configured modules directory pnpm/tasks#230.pnpm store prunenow removes aliases of pruned packages.pnpm store statusno longer reports untouched packages as modified when the global virtual store is enabled. If the installed global-store layout cannot be verified, the command reportsERR_PNPM_STORE_STATUS_UNVERIFIABLEand asks for a reinstall #17631.pnpm store addnow fails withERR_PNPM_FROZEN_STORE_WRITEwhenfrozenStoreis enabled. It used to write package files into the read-only store without recording them, so no install could use them.pnpm cat-index <name>@<version>no longer shows the index of a package whose name differs only in letter case.Other commands and settings
pnpm linknow fails without changingpackage.jsonorpnpm-workspace.yamlwhen the linked package's name is not a valid npm package name. It used to write that name to both files, which made every later install fail #17475.pnpm link <dir>now resolves a relative<dir>against the current directory. In a directory without apackage.json, such as a workspace'spackagesConfiguration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.