Skip to content

chore(deps): update pnpm to v11.28.12 - #369

Open
renovate[bot] wants to merge 1 commit into
masterfrom
renovate/pnpm-11.x
Open

renovate[bot] wants to merge 1 commit into
masterfrom
renovate/pnpm-11.x

Conversation

@renovate

@renovate renovate Bot commented Jul 27, 2026 •

Copy link
Copy Markdown
Contributor

Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence
pnpm (source) 11.7.0+sha512.19cc852c120c7125760f2443ee6be0ca5b40f9f50598de1a09a1f177503e010e57c23c77646e01e761de59bf874fb22a3398c33ab9691fc13eb946b6f0f4d620 → 11.28.12 age confidence

Release Notes

pnpm/pnpm (pnpm)

v11.28.12: pnpm 11.28.12

Compare Source

pnpm 11.28.12 fixes many peer dependency, pnpm deploy, frozen-lockfile, and nodeLinker: hoisted bugs. It also includes a security fix. A ${VAR} placeholder in a repository's registry URL now fails the command, so pnpm no longer sends those requests to another registry. The bundled node-gyp no longer ships the undici version that security scanners flag, and remote resolution needs pnpr 0.1.0-alpha.20 or newer.

Patch Changes
Upgrading and security
  • A ${VAR} placeholder in a registry URL in pnpm-workspace.yaml or the project .npmrc now 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, or userAgent setting in pnpm-workspace.yaml #​17762.

  • The node-gyp bundled with pnpm no longer ships undici 6, which security scanners flag for CVE-2026-84947. On Node.js 26, node-gyp downloads through a proxy or with a custom CA file no longer crash with "invalid onError method" #​17941.

  • Remote resolution and shared build caches no longer work with pnpr 0.1.0-alpha.19 or older. pnpm now reads the capabilities a pnpr server advertises under pnpr.protocols. Installs fail when the server does not confirm the requested resolution and verification policies. Upgrade the pnpr server before upgrading pnpm.

Installs that failed
  • pnpm install --frozen-lockfile now succeeds when a workspace project recorded in pnpm-lock.yaml has an empty directory, such as a git submodule that was not checked out #​17712.

  • pnpm install --frozen-lockfile now accepts a lockfile when an injected workspace package declares a file: or link: dependency with backslashes, such as file:..\vendor, or with a slash after the protocol, such as file:/./vendor. Before, the install reported the lockfile as out of date right after pnpm install had written it #​17720.

  • pnpm install --frozen-lockfile and verifyDepsBeforeRun now accept a workspace: dependency on a project whose version is not valid semver, such as workspace:1 on a project at version 1. Before, they reported the lockfile that pnpm install had just written as out of date.

  • pnpm fetch no longer fails with ENOENT when nodeLinker is hoisted and the project configures patchedDependencies or allowBuilds. pnpm fetch also preserves an existing hoisted node_modules directory #​18037.

  • Git dependencies now accept npm's :: separator between fragment parameters, such as github:owner/repo#v1.0.0::path:packages/foo. Before, pnpm read the whole fragment as a branch name and failed to resolve it #​17827.

  • pnpm no longer fails to remove a dependency whose package.json is malformed. It removes the dependency and keeps its bins pnpm/tasks#295.

  • Fixed pnpm deprecate, pnpm undeprecate, and pnpm unpublish failing with revision conflicts when a registry cache serves stale package metadata.

  • When a package injected through a path, such as file:../lib or ../lib, gives one of its dependencies a catalog: specifier, pnpm install now fails the way a fresh resolution does, and pnpm install --frozen-lockfile reports the lockfile as outdated. Before, both could accept the existing lockfile #​17722.

Peer dependencies
  • Repeated installs no longer change the peer dependency providers that the previous install chose. This covers adding a dependency, removing a shared package from one workspace project, and projects that use different ranges of one dependency pnpm/tasks#221.

    An unchanged install keeps a valid locked peer provider even when a direct dependency provides another compatible version. Explicit pnpm add and pnpm update requests take precedence over it. Required dependencies no longer remain marked optional when another workspace project removes a shared package.

  • Workspace projects that select different versions of a peer provider no longer share one copy of the package that depends on it. This affected peers reached through an aliased dependency or a peer dependency cycle.

  • New workspace projects now prefer peer versions already pinned in the lockfile. Dependencies that are also optional peers no longer cause an unrelated project to select an older peer version.

  • 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 if resolvePeersFromWorkspaceRoot is true. Before, a tool in one project's devDependencies, such as webpack-cli, could become an optional peer of another project's production dependencies #​16666.

  • pnpm install no longer gives a project an optional peer dependency that it skipped because a required peer would conflict with the project's dependencies. Before, dedupePeerDependents merged the project's copy of the package that declares the peer with another project's copy that resolves it #​17781.

  • pnpm install no 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.

  • With autoInstallPeersFromHighestMatch, conflicting non-semver peer dependencies now remain missing, and identical non-semver peer specifiers are preserved. Preferred registry versions no longer replace local paths or protocol-prefixed specifiers when pnpm installs missing peers pnpm/tasks#272.

  • Fixed installation and peer dependency reporting for packages named constructor or toString. Optional peers with these names are also recognized when declared only in peerDependenciesMeta.

Resolving and linking dependencies
  • A root overrides entry that points a package at a workspace: path, such as workspace:./packages/foo, now also applies when a registry package depends on that package pnpm/tasks#270.

  • Version-selector overrides entries such as "ms@^2.0.0": "2.1.1" now apply to dependencies declared with the catalog: protocol when the catalog entry's range matches the selector #​17922.

  • An optional dependency that declares no os, cpu, or libc field is no longer skipped because its name contains only an operating system word, such as get-windows on 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.

  • pnpm dedupe now keeps a locked runtime version, from devEngines.runtime or from a dependency's engines.runtime, when the declared range still admits it. pnpm dedupe --check no longer fails each time a newer Node.js release in the range comes out #​17984.

  • 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.

  • Dependencies declared as workspace: entries in catalogs now remain in the lockfile when excludeLinksFromLockfile is enabled. Frozen installs can restore these links after node_modules is removed pnpm/tasks#260.

  • pnpm install --filter in 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.

  • With nodeLinker: hoisted, pnpm install --filter in a sparse checkout now drops previously installed workspace projects that are missing from disk from the hoisted node_modules tree. It no longer recreates node_modules inside a missing project's directory. Packages that only the missing project used are also removed from the root node_modules.

  • With nodeLinker: hoisted and a custom modulesDir, pnpm now installs a workspace project's dependencies that cannot be hoisted to the root into the project's modulesDir. The next install that relinks the project removes the copies that earlier installs left in its node_modules. A later install restores the project's modulesDir when it was removed. Package directories that pnpm did not install are now also moved to .ignored in a custom modulesDir.

  • With dedupeDirectDeps, pnpm install now compares link: dependencies by the directory they point at. A project's link: dependency is removed when the workspace root links the same directory under a different path. It is kept when the root's link: dependency has the same text but points at another directory. This also applies with nodeLinker: hoisted.

    pnpm install reports each removed link: dependency once pnpm/tasks#293.

  • A repeat pnpm install with nodeLinker: pnp now applies dependency and configuration changes. Before, it printed "Already up to date" and left the lockfile unchanged.

  • Config dependencies use the declared registry serverType when recording and installing packages pnpm/tasks#236.

pnpm deploy
  • pnpm deploy no longer fails when the deployed project depends on a workspace package that sets publishConfig.directory. pnpm installs that package from its publish directory and runs its build scripts #​17771.

  • pnpm deploy now runs the build scripts of a workspace project that it installs as a file: dependency, without a machine-specific allowBuilds key. An allowBuilds entry that denies the project still applies #​17740.

  • pnpm deploy --offline --trust-lockfile now 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.

  • pnpm deploy preserves an injected workspace package's resolved dependencies when they differ from the workspace project's own dependencies. This also applies to packages with publishConfig.directory pnpm/tasks#221.

  • pnpm deploy now binds optional peers declared only in peerDependenciesMeta for linked workspace packages. The deployed manifest and lockfile also retain these peers when filtering dependency groups.

Builds, bins, and scripts
  • 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-scripts links the packages it does not build from their own store directories, and pnpm store prune removes 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. This includes git dependencies that an older pnpm marked in a shared store as not requiring a build pnpm/tasks#189.

  • Fixed pnpm store status reporting approved builds of git dependencies as modified when the store contains legacy build metadata.

  • pnpm store prune now stops if a dependency link cannot be read. This keeps installed packages from being removed after an incomplete scan.

  • When pnpm install adds placeholder entries to allowBuilds in pnpm-workspace.yaml, it no longer copies allowBuilds entries from other config sources into the file.

  • Bin shims in the global virtual store no longer include the hoisted modules directory of the project that installed them #​18035.

  • POSIX bin shims and the pnpm, pn, pnpx, and pnx launchers now run inside a Nix build on macOS with the sandbox enabled. Installing again replaces the shims already in node_modules #​17750.

  • Installing no longer replaces the POSIX bin shims that a newer pnpm wrote in node_modules/.bin.

  • Linking bins is faster for packages that ship large native executables as bins. pnpm now reads only the first 512 bytes of a bin file to find its shebang #​17361.

  • pnpm run and pnpm setup no longer clear the visible terminal on Windows when a project path contains non-ASCII characters.

  • pnpm stops scripts and their descendants when it is killed during script startup pnpm/tasks#313.

Engines and runtimes
  • pnpm install now fails on a workspace project's incompatible engines.pnpm, or on its incompatible engines.node with engineStrict enabled, even when the project's os, cpu, or libc excludes the current platform pnpm/tasks#281.

  • pnpm install now checks the project's engines field when the project is already up to date. A repeat install of a project outside a workspace warns about an incompatible Node.js version, or fails with engineStrict enabled #​17751.

  • A workspace project that downloads its own Node.js through devEngines.runtime now has its engines.node checked against that Node.js. Before, pnpm checked it against the shared Node.js version, so engineStrict could reject a project whose scripts run on a compatible runtime pnpm/tasks#300.

  • A repeat pnpm install now runs a full install when the runtimeOnFail setting changes. Before, it printed "Already up to date" and did not install the runtime a project declares in devEngines.runtime pnpm/tasks#303.

  • Fixed missing warnings when a required dependency does not support the current Node.js version.

Other commands and settings
  • pnpm dist-tag and pnpm unpublish now 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 login now prints the registry's npm-notice message before the web login URL. Some registries use it to show a code that you type in the browser.

  • pnpm self-update now updates the project's engines.pnpm range along with its pnpm pin, keeping the ^ or ~ operator #​17732.

  • pnpm setup and the install script now support PowerShell as the login shell on Linux and macOS. They add PNPM_HOME to PATH in profile.ps1 under $XDG_CONFIG_HOME/powershell or ~/.config/powershell #​18026.

  • pnpm setup rejects a PNPM_HOME value that would split the saved PATH pnpm/tasks#315.

  • Relative directory selectors set on config.filter or config.filterProd by an updateConfig hook now resolve from the workspace root even when --dir is passed or pnpm runs from a subdirectory #​17906.

  • pnpm now reads the boot document of pnpm-lock.yaml when it is written in lockfile format 13. pnpm then switches to the pnpm version such a project pins.

  • Programmatic install mutations that omit workspace project manifests now resolve locally when a pnpr server is configured pnpm/tasks#59.

  • pnpm now recognizes Capawesome Cloud and RWX as CI environments.

  • The warning about unrecognized settings now marks projectScopedOptionalPeers as a setting of a newer pnpm version.

Platinum Sponsors

Bit OpenAI Notion
CodeRabbit Cloudflare

Gold Sponsors

Sanity Discord Vite
SerpApi Stackblitz Workleap
Nx Latitude Syntax

v11.28.11: pnpm 11.28.11

Compare Source

pnpm 11.28.11 fixes frozen installs with excludeLinksFromLockfile, pnpm link in workspaces, pnpm deploy with dangling symlinks, and verifyDepsBeforeRun starting needless installs.

Patch Changes
Installing packages
  • pnpm deploy now keeps a symlink in the project whose target is missing from the source, such as a link into a node_modules directory that was removed after the build. Deploy used to fail with ENOENT on such a link #​17571.

  • A package with bundledDependencies and a build script now keeps its bundled dependencies when it is restored from the side-effects cache #​17523.

  • pnpm install now links the runtime that an earlier pnpm install --no-runtime skipped #​17542.

  • Commands of a package whose bin paths 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.

  • A repeat pnpm install now rewrites the bin shims after extendNodePath changes. Before, it reported "Already up to date" and the shims kept the NODE_PATH of the previous setting.

Lockfile and resolution
  • pnpm install --frozen-lockfile now accepts the lockfile it wrote with excludeLinksFromLockfile and linkWorkspacePackages on, when a project depends on a workspace package through a plain version range or a catalog: entry. It used to fail with ERR_PNPM_OUTDATED_LOCKFILE.

  • pnpm install --frozen-lockfile, pnpm approve-builds, and pnpm rebuild now accept a lockfile that resolves a * dependency to a prerelease latest version. pnpm wrote such a lockfile and then reported it as outdated #​17594.

  • Packages from the default registry keep plain lockfile keys, even when a prefix such as npmjs points at the registry set as registry. 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.

  • Relative local paths in root overrides now 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.

  • 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.

  • A Node.js version range such as >=26.13, for example in devEngines.runtime, now resolves to the newest stable release that satisfies it. pnpm picks a prerelease only when no stable release matches #​17516.

verifyDepsBeforeRun
  • With verifyDepsBeforeRun, pnpm run and pnpm exec now report dependencies as out of date after a dependency is added to the package.json of a local directory dependency, such as "lib": "file:../lib". Before, the command ran without the new dependency installed.

  • verifyDepsBeforeRun no longer reports dependencies as out of sync when only the version field 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.

pnpm link
  • In a workspace, pnpm link <dir> now adds the link: dependency to the package.json of the project where the command runs, not to the workspace root's package.json. The link is created in that project's node_modules, as documented. The override is still written to the root pnpm-workspace.yaml.

  • pnpm link with several paths now records every linked package in the overrides of pnpm-workspace.yaml. Some of them could be missing before.

  • pnpm link now fails without changing package.json or pnpm-workspace.yaml when 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 update
  • pnpm update with only negated selectors, such as pnpm update '!foo', now leaves the dependencies listed in update.ignoreDeps unchanged pnpm/tasks#243.

  • pnpm update --depth 0 without selectors now does nothing when every direct dependency is listed in update.ignoreDeps. Before, it failed with ERR_PNPM_NO_PACKAGE_IN_DEPENDENCIES pnpm/tasks#251.

Store and self-update
  • pnpm store prune now keeps packages linked from a configured modules directory pnpm/tasks#230.

  • pnpm store status no longer reports untouched packages as modified when the global virtual store is enabled. If the installed global-store layout cannot be verified, the command reports ERR_PNPM_STORE_STATUS_UNVERIFIABLE and asks for a reinstall #​17631.

  • pnpm store add now fails right away with ERR_PNPM_FROZEN_STORE_WRITE when frozenStore is enabled. It used to retry each download for minutes before failing, or fail with a SQLite error on an empty store.

  • pnpm self-update now reinstalls a cached engine if its executable cannot run. This repairs shared store entries damaged by an earlier install #​17582.

Platinum Sponsors

Bit OpenAI Notion
CodeRabbit Cloudflare

Gold Sponsors

Sanity Discord Vite
SerpApi Stackblitz Workleap
Nx Latitude Syntax

v11.28.10: pnpm 11.28.10

Compare Source

pnpm 11.28.10 stops pnpm store prune from deleting other stores when cacheDir points to their parent directory. It also fixes globally installed commands that load hoisted dependencies, and repeat installs that missed changes to local dependencies.

Patch Changes
Installing packages
  • pnpm store prune preserves other stores and global package data when cacheDir points to their parent directory.

  • Commands installed with pnpm add --global now find the dependencies that pnpm hoists for their package. A package that loads a dependency it does not declare, such as a native addon's platform-specific package, failed with "Cannot find module". Reinstall such a package with pnpm add --global to update its existing command #​17503.

  • pnpm prune --prod no longer fails with ERR_PNPM_EXDEV when node_modules was copied from an earlier Docker build stage #​17424.

  • pnpm install now retries a Node.js runtime zip download when the connection drops partway through. A download that still fails names its URL. Before, a single dropped connection ended the install with terminated #​17411.

  • With the global virtual store, a change to a dependency of one package in a dependency cycle now gives every package in that cycle a new directory. Before, the other packages kept their directories and still linked the old copy of the changed package, so the project could load two copies of it #​17466.

    Packages in a dependency cycle, and packages that depend on one, move to new global virtual store directories once after this update. Those that run a build miss the side-effects cache once.

  • pnpm install and pnpm rebuild now refresh privately hoisted .bin shims in node_modules/.pnpm/node_modules/.bin after a dependency build replaces a script target with a native executable #​17402.

  • The Node.js latest selector now chooses the newest stable release #​17490.

  • The standalone @pnpm/exe builds now embed Node.js 26.13.0.

Repeat installs and lockfiles
  • pnpm install now resolves a local directory again after its package.json changes when an override or a package extension adds it to the dependencies of a registry package. pnpm install --frozen-lockfile fails on a lockfile that still records the old dependencies of such a directory #​17486.

  • With injectWorkspacePackages and per-project lockfiles, pnpm install now updates a project's lockfile when a local tarball that an injected workspace project depends on is replaced. The project's lockfile kept the old version and integrity before.

  • pnpm install now detects a change to a local tarball or directory that only a pnpmfile readPackage hook depends on. A repeat install reported "Already up to date" and kept the old contents before pnpm/tasks#227.

  • pnpm install now relinks a workspace: or link: dependency whose link was deleted from node_modules. It used to report "Already up to date" and leave the link missing #​17485.

  • Merging git branch lockfiles now keeps a workspace project whose directory is named __proto__. It was dropped from the merged lockfile before pnpm/tasks#59.

Adding and publishing packages
  • pnpm add no longer rewrites a catalog entry set to the dist-tag that the dependency resolves through. For example, an entry beta stays beta after pnpm add foo@beta or pnpm add foo. Before, the entry was replaced with the version the tag pointed to pnpm/tasks#225.

  • pnpm pack and pnpm publish now always include the binary file declared by a string bin field in package.json, even when files or .npmignore would otherwise exclude it.

  • When the version or range given to pnpm unpublish matches every published version, the error now says so and shows the same command with --force. It suggested running pnpm unpublish <pkg>@<version>, the command that had just failed.

Running commands
  • Every command, including pnpm --version, pnpm self-update, and invocations with unknown flags, now applies the same packageManager and devEngines.packageManager settings when switching to the pinned pnpm version or recording it in pnpm-lock.yaml. --config.<key> flags and lockfileDir now reach the version switch and lockfile sync on every entry point. Unreadable settings in pnpm-workspace.yaml or the global config.yaml that do not affect the pin decision no longer block the version switch pnpm/tasks#222.

  • On Windows, the shell shim of a .cmd or .bat bin now runs it under Git Bash when MSYS argument conversion is off, such as with MSYS_NO_PATHCONV=1 or MSYS2_ARG_CONV_EXCL='*'. The shim used to start an interactive cmd.exe prompt #​17480.

  • pnx and pnpm create now run the command in the directory selected by --dir or --workspace-root. Without either flag, the command still runs in the directory pnpm was started in.

  • The error for a dependency with an invalid name in a project's manifest now names the project's directory. It used to say only "The current package", which did not tell which workspace project to fix #​17475.

Platinum Sponsors

Bit OpenAI Notion
CodeRabbit Cloudflare

Gold Sponsors

Sanity Discord Vite
SerpApi Mend Renovate. View the repository job log.

@renovate renovate Bot added the dependencies Pull requests that update a dependency file label Jul 27, 2026
@renovate
renovate Bot force-pushed the renovate/pnpm-11.x branch 2 times, most recently from 3cc414b to 973397a Compare July 29, 2026 20:29
@renovate renovate Bot changed the title chore(deps): update pnpm to v11.15.1 chore(deps): update pnpm to v11.16.0 Jul 29, 2026
@renovate
renovate Bot force-pushed the renovate/pnpm-11.x branch from 973397a to e171318 Compare July 30, 2026 20:14
@renovate renovate Bot changed the title chore(deps): update pnpm to v11.16.0 chore(deps): update pnpm to v11.17.0 Jul 30, 2026
@renovate
renovate Bot force-pushed the renovate/pnpm-11.x branch 2 times, most recently from 51d3b39 to 5296c8a Compare August 5, 2026 10:34
@renovate renovate Bot changed the title chore(deps): update pnpm to v11.17.0 chore(deps): update pnpm to v11.18.0 Aug 5, 2026
@renovate
renovate Bot force-pushed the renovate/pnpm-11.x branch from 5296c8a to ac55239 Compare August 7, 2026 09:46
@renovate renovate Bot changed the title chore(deps): update pnpm to v11.18.0 chore(deps): update pnpm to v11.19.0 Aug 7, 2026
@renovate
renovate Bot force-pushed the renovate/pnpm-11.x branch 2 times, most recently from 70d6a25 to d9a724d Compare August 10, 2026 14:59
@renovate renovate Bot changed the title chore(deps): update pnpm to v11.19.0 chore(deps): update pnpm to v11.20.0 Aug 10, 2026
@renovate
renovate Bot force-pushed the renovate/pnpm-11.x branch 4 times, most recently from 38ae4fe to 0990c5a Compare August 16, 2026 14:43
@renovate renovate Bot changed the title chore(deps): update pnpm to v11.20.0 chore(deps): update pnpm to v11.21.0 Aug 16, 2026
@renovate
renovate Bot force-pushed the renovate/pnpm-11.x branch from 0990c5a to d3e2085 Compare August 22, 2026 18:14
@renovate renovate Bot changed the title chore(deps): update pnpm to v11.21.0 chore(deps): update pnpm to v11.22.0 Aug 22, 2026
@renovate
renovate Bot force-pushed the renovate/pnpm-11.x branch from d3e2085 to a0f05d9 Compare August 30, 2026 18:29
@renovate renovate Bot changed the title chore(deps): update pnpm to v11.22.0 chore(deps): update pnpm to v11.23.0 Aug 30, 2026
@renovate
renovate Bot force-pushed the renovate/pnpm-11.x branch from a0f05d9 to 3653b0c Compare August 31, 2026 15:57
@renovate renovate Bot changed the title chore(deps): update pnpm to v11.23.0 chore(deps): update pnpm to v11.24.0 Aug 31, 2026
@renovate
renovate Bot force-pushed the renovate/pnpm-11.x branch 2 times, most recently from 80350de to 419d959 Compare September 5, 2026 14:32
@renovate renovate Bot changed the title chore(deps): update pnpm to v11.24.0 chore(deps): update pnpm to v11.25.0 Sep 5, 2026
@renovate
renovate Bot force-pushed the renovate/pnpm-11.x branch 2 times, most recently from 304cebb to 73f61ff Compare September 11, 2026 15:05
@renovate
renovate Bot force-pushed the renovate/pnpm-11.x branch from 45c499d to d324c33 Compare October 5, 2026 08:45
@renovate renovate Bot changed the title chore(deps): update pnpm to v11.28.0 chore(deps): update pnpm to v11.28.1 Oct 5, 2026
@renovate
renovate Bot force-pushed the renovate/pnpm-11.x branch from d324c33 to fb61e00 Compare October 5, 2026 22:43
@renovate renovate Bot changed the title chore(deps): update pnpm to v11.28.1 chore(deps): update pnpm to v11.28.2 Oct 5, 2026
@renovate
renovate Bot force-pushed the renovate/pnpm-11.x branch 2 times, most recently from e3b0a89 to ad58e9e Compare October 7, 2026 17:14
@renovate renovate Bot changed the title chore(deps): update pnpm to v11.28.2 chore(deps): update pnpm to v11.28.3 Oct 7, 2026
@renovate
renovate Bot force-pushed the renovate/pnpm-11.x branch from ad58e9e to e14e6da Compare October 11, 2026 01:26
@renovate renovate Bot changed the title chore(deps): update pnpm to v11.28.3 chore(deps): update pnpm to v11.28.4 Oct 11, 2026
@renovate
renovate Bot force-pushed the renovate/pnpm-11.x branch from e14e6da to 50ea4fc Compare October 13, 2026 06:13
@renovate renovate Bot changed the title chore(deps): update pnpm to v11.28.4 chore(deps): update pnpm to v11.28.5 Oct 13, 2026
@renovate
renovate Bot force-pushed the renovate/pnpm-11.x branch 2 times, most recently from f27ba5b to 3e91a62 Compare October 22, 2026 18:37
@renovate renovate Bot changed the title chore(deps): update pnpm to v11.28.5 chore(deps): update pnpm to v11.28.6 Oct 22, 2026
@renovate
renovate Bot force-pushed the renovate/pnpm-11.x branch 3 times, most recently from 08efadf to 15e3ecc Compare October 28, 2026 16:53
@renovate renovate Bot changed the title chore(deps): update pnpm to v11.28.6 chore(deps): update pnpm to v11.28.7 Oct 28, 2026
@renovate
renovate Bot force-pushed the renovate/pnpm-11.x branch from 15e3ecc to 42cda9a Compare October 29, 2026 23:35
@renovate renovate Bot changed the title chore(deps): update pnpm to v11.28.7 chore(deps): update pnpm to v11.28.8 Oct 29, 2026
@renovate
renovate Bot force-pushed the renovate/pnpm-11.x branch from 42cda9a to e35f1c9 Compare November 3, 2026 01:48
@renovate renovate Bot changed the title chore(deps): update pnpm to v11.28.8 chore(deps): update pnpm to v11.28.9 Nov 3, 2026
@renovate
renovate Bot force-pushed the renovate/pnpm-11.x branch 2 times, most recently from 530bdef to 7cf209c Compare November 6, 2026 19:27
@renovate renovate Bot changed the title chore(deps): update pnpm to v11.28.9 chore(deps): update pnpm to v11.28.10 Nov 6, 2026
@renovate
renovate Bot force-pushed the renovate/pnpm-11.x branch from 7cf209c to d5e597a Compare November 12, 2026 02:49
@renovate renovate Bot changed the title chore(deps): update pnpm to v11.28.10 chore(deps): update pnpm to v11.28.11 Nov 12, 2026
@renovate
renovate Bot force-pushed the renovate/pnpm-11.x branch from d5e597a to 2394678 Compare November 20, 2026 22:24
@renovate renovate Bot changed the title chore(deps): update pnpm to v11.28.11 chore(deps): update pnpm to v11.28.12 Nov 20, 2026

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants