chore(release): 11.27.1 (#15185)

Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
2026-09-21 05:45:12 -04:00 · 2026-09-20 23:11:14 +02:00
1 parent 8cf342a051
commit 201f9fc51f
@@ -0,0 +1,8 @@
+## 1100.0.31
+
+### Patch Changes
+
+- Updated dependencies:
+  - @pnpm/assert-store@1100.0.31
+  - @pnpm/installing.modules-yaml@1101.0.3
+  - @pnpm/lockfile.types@1100.1.2
@@ -0,0 +1,6 @@
+## 1100.0.31
+
+### Patch Changes
+
+- Updated dependencies:
+  - @pnpm/store.cafs@1100.3.3
@@ -0,0 +1,9 @@
+## 1100.3.9
+
+### Patch Changes
+
+- Updated dependencies:
+  - @pnpm/cli.utils@1101.0.28
+  - @pnpm/config.reader@1102.2.1
+  - @pnpm/network.fetch@1100.1.17
+  - @pnpm/registry-access.client@1100.1.19
@@ -0,0 +1,12 @@
+## 1100.0.0
+
+### Patch Changes
+
+- The `@zkochan/cmd-shim` package is now available as `@pnpm/bins.cmd-shim`.
+
+- POSIX bin shims now convert a Windows-form path such as `C:\node_modules\.bin\tsc` correctly. The shim mangled the backslashes in such a path and could not reach the package it runs. Installing again replaces the shims already in `node_modules` [#14867](https://github.com/pnpm/pnpm/issues/14867).
+
+- POSIX bin shims now take `cygpath` and `wslpath` from the system default path on Cygwin, MSYS2, and WSL2. The shims looked both helpers up on `PATH`, where a dependency's own bins come first, so a dependency could redirect another package's shim. Installing again replaces the shims already in `node_modules` [#14866](https://github.com/pnpm/pnpm/issues/14866).
+
+- Updated dependencies:
+  - @pnpm/fs.graceful-fs@1100.2.2
@@ -0,0 +1,17 @@
+## 1100.0.32
+
+### Patch Changes
+
+- The `@zkochan/cmd-shim` package is now available as `@pnpm/bins.cmd-shim`.
+
+- `pnpm add -g` and `pnpm update -g` now ignore incomplete unrelated global package groups when every command from the replaced group is retained. Operations that could remove a global command still require complete ownership information.
+
+- A dependency's own bins can no longer take over another package's bin shim. The POSIX shims pnpm generates used to look up their shell helpers on `PATH`, where a dependency's bins come first [#14837](https://github.com/pnpm/pnpm/issues/14837). Reinstalling replaces the shims already in your `node_modules`. On Cygwin, MSYS2, and WSL the shims still take their Windows path conversion from `PATH`, so a dependency can still redirect them there.
+
+- POSIX bin shims now convert a Windows-form path such as `C:\node_modules\.bin\tsc` correctly. The shim mangled the backslashes in such a path and could not reach the package it runs. Installing again replaces the shims already in `node_modules` [#14867](https://github.com/pnpm/pnpm/issues/14867).
+
+- POSIX bin shims now take `cygpath` and `wslpath` from the system default path on Cygwin, MSYS2, and WSL2. The shims looked both helpers up on `PATH`, where a dependency's own bins come first, so a dependency could redirect another package's shim. Installing again replaces the shims already in `node_modules` [#14866](https://github.com/pnpm/pnpm/issues/14866).
+
+- Updated dependencies:
+  - @pnpm/pkg-manifest.utils@1100.4.5
+  - @pnpm/workspace.project-manifest-reader@1100.0.29
@@ -0,0 +1,6 @@
+## 1100.0.24
+
+### Patch Changes
+
+- Updated dependencies:
+  - @pnpm/core-loggers@1101.0.0
@@ -0,0 +1,21 @@
+## 1103.0.5
+
+### Patch Changes
+
+- Updated dependencies:
+  - @pnpm/bins.linker@1100.0.32
+  - @pnpm/building.policy@1100.1.2
+  - @pnpm/config.reader@1102.2.1
+  - @pnpm/core-loggers@1101.0.0
+  - @pnpm/deps.graph-hasher@1100.3.3
+  - @pnpm/deps.path@1101.0.3
+  - @pnpm/exec.lifecycle@1100.1.18
+  - @pnpm/fs.symlink-dependency@1100.0.20
+  - @pnpm/installing.context@1101.0.5
+  - @pnpm/installing.modules-yaml@1101.0.3
+  - @pnpm/lockfile.types@1100.1.2
+  - @pnpm/lockfile.utils@1102.1.3
+  - @pnpm/lockfile.walker@1100.0.24
+  - @pnpm/store.cafs@1100.3.3
+  - @pnpm/store.connection-manager@1101.1.3
+  - @pnpm/store.controller-types@1101.3.0
@@ -0,0 +1,15 @@
+## 1101.2.3
+
+### Patch Changes
+
+- Updated dependencies:
+  - @pnpm/building.after-install@1103.0.5
+  - @pnpm/building.policy@1100.1.2
+  - @pnpm/cli.utils@1101.0.28
+  - @pnpm/config.reader@1102.2.1
+  - @pnpm/config.writer@1100.0.27
+  - @pnpm/deps.path@1101.0.3
+  - @pnpm/global.packages@1101.1.3
+  - @pnpm/installing.commands@1101.3.1
+  - @pnpm/installing.modules-yaml@1101.0.3
+  - @pnpm/store.connection-manager@1101.1.3
@@ -0,0 +1,15 @@
+## 1102.2.2
+
+### Patch Changes
+
+- Updated dependencies:
+  - @pnpm/bins.linker@1100.0.32
+  - @pnpm/config.reader@1102.2.1
+  - @pnpm/core-loggers@1101.0.0
+  - @pnpm/deps.graph-hasher@1100.3.3
+  - @pnpm/deps.path@1101.0.3
+  - @pnpm/exec.lifecycle@1100.1.18
+  - @pnpm/fs.hard-link-dir@1100.0.6
+  - @pnpm/lockfile.types@1100.1.2
+  - @pnpm/pnpr.client@3.0.3
+  - @pnpm/store.controller-types@1101.3.0
@@ -0,0 +1,6 @@
+## 1100.1.2
+
+### Patch Changes
+
+- Updated dependencies:
+  - @pnpm/deps.path@1101.0.3
@@ -0,0 +1,10 @@
+## 1100.0.44
+
+### Patch Changes
+
+- `pnpm cache list-registries` now prints the registry URL, matching `pnpm cache view`. It printed `https%3A+registry.npmjs.org` before and prints `https://registry.npmjs.org/` now [#15046](https://github.com/pnpm/pnpm/issues/15046).
+
+- Updated dependencies:
+  - @pnpm/config.reader@1102.2.1
+  - @pnpm/resolving.npm-resolver@1104.2.0
+  - @pnpm/store.cafs@1100.3.3
@@ -0,0 +1,8 @@
+## 1100.1.6
+
+### Patch Changes
+
+- Updated dependencies:
+  - @pnpm/cache.api@1100.0.44
+  - @pnpm/cli.utils@1101.0.28
+  - @pnpm/config.reader@1102.2.1
@@ -0,0 +1,10 @@
+## 1100.0.43
+
+### Patch Changes
+
+- Fixed shell completion of package scripts for `pnpm run` and `pnpm run-script` [pnpm/pnpm#15034](https://github.com/pnpm/pnpm/issues/15034).
+
+  Bash completion now preserves literal script names containing glob characters and shell punctuation in pnpm v11 and v12.
+
+- Updated dependencies:
+  - @pnpm/config.reader@1102.2.1
@@ -0,0 +1,21 @@
+## 1100.3.20
+
+### Patch Changes
+
+- Install warnings no longer carry the text of a package's deprecation notice. The warning names the deprecated package and version, and the `pnpm:deprecation` event no longer carries the notice either. `pnpm view` still shows it on request.
+
+  A deprecation warning now names the newest version of the package that is not deprecated, and says when reaching it means widening the range you declared:
+
+  ```
+  WARN  deprecated foo@1.0.0. 2.3.1 is not deprecated, outside the range you declared.
+  ```
+
+  pnpm works this out from the metadata it already fetched, so it costs no extra request. An install that reuses the lockfile without fetching metadata names no version.
+
+  pnpm strips control characters from the package name and version in a deprecation warning, and from the notice `pnpm outdated --long` prints.
+
+  The text sanitizer now also strips the Unicode line and paragraph separators U+2028 and U+2029.
+
+- Updated dependencies:
+  - @pnpm/core-loggers@1101.0.0
+  - @pnpm/text.sanitize@1100.0.1
@@ -0,0 +1,6 @@
+## 1100.1.12
+
+### Patch Changes
+
+- Updated dependencies:
+  - @pnpm/workspace.root-finder@1100.0.9
@@ -0,0 +1,8 @@
+## 1101.0.28
+
+### Patch Changes
+
+- Updated dependencies:
+  - @pnpm/config.package-is-installable@1100.1.7
+  - @pnpm/pkg-manifest.utils@1100.4.5
+  - @pnpm/workspace.project-manifest-reader@1100.0.29
@@ -0,0 +1,8 @@
+## 1101.0.5
+
+### Patch Changes
+
+- Updated dependencies:
+  - @pnpm/cli.utils@1101.0.28
+  - @pnpm/config.reader@1102.2.1
+  - @pnpm/workspace.workspace-manifest-writer@1100.2.1
@@ -0,0 +1,6 @@
+## 1100.1.7
+
+### Patch Changes
+
+- Updated dependencies:
+  - @pnpm/core-loggers@1101.0.0
@@ -0,0 +1,15 @@
+## 1102.2.1
+
+### Patch Changes
+
+- Warnings about ignored environment variables in project `.npmrc` credentials now link to the npmrc documentation [pnpm/pnpm#15051](https://github.com/pnpm/pnpm/issues/15051).
+
+- pnpm now reads a `pnpm-workspace.yaml` whose `tasks` section uses a setting only pnpm 12 acts on, such as `concurrencyGroup`. A task's unrecognized fields are ignored, unless the field only differs in case from `concurrency` or `dependsOn`, which pnpm reports as a typo.
+
+  The warning about unrecognized top-level settings now names `cargo`, `concurrencyGroups`, and `pipelines` as pnpm 12 settings.
+
+- Updated dependencies:
+  - @pnpm/hooks.pnpmfile@1100.0.32
+  - @pnpm/network.git-utils@1100.0.4
+  - @pnpm/pkg-manifest.utils@1100.4.5
+  - @pnpm/workspace.project-manifest-reader@1100.0.29
@@ -0,0 +1,6 @@
+## 1100.0.27
+
+### Patch Changes
+
+- Updated dependencies:
+  - @pnpm/workspace.workspace-manifest-writer@1100.2.1
@@ -0,0 +1,17 @@
+## 1101.0.0
+
+### Major Changes
+
+- Install warnings no longer carry the text of a package's deprecation notice. The warning names the deprecated package and version, and the `pnpm:deprecation` event no longer carries the notice either. `pnpm view` still shows it on request.
+
+  A deprecation warning now names the newest version of the package that is not deprecated, and says when reaching it means widening the range you declared:
+
+  ```
+  WARN  deprecated foo@1.0.0. 2.3.1 is not deprecated, outside the range you declared.
+  ```
+
+  pnpm works this out from the metadata it already fetched, so it costs no extra request. An install that reuses the lockfile without fetching metadata names no version.
+
+  pnpm strips control characters from the package name and version in a deprecation warning, and from the notice `pnpm outdated --long` prints.
+
+  The text sanitizer now also strips the Unicode line and paragraph separators U+2028 and U+2029.
@@ -0,0 +1,6 @@
+## 1100.0.5
+
+### Patch Changes
+
+- Updated dependencies:
+  - @pnpm/fs.graceful-fs@1100.2.2
@@ -0,0 +1,8 @@
+## 1100.2.5
+
+### Patch Changes
+
+- Resolving a Node.js runtime now fails when unofficial-builds.nodejs.org cannot be reached. pnpm used to ignore that failure and leave the musl builds out of `pnpm-lock.yaml`. `pnpm update` then wrote a different lockfile on a machine whose network blocks the mirror [pnpm/pnpm#14813](https://github.com/pnpm/pnpm/issues/14813).
+
+- Updated dependencies:
+  - @pnpm/crypto.hash@1100.0.5
@@ -0,0 +1,12 @@
+## 1101.0.37
+
+### Patch Changes
+
+- Updated dependencies:
+  - @pnpm/deps.path@1101.0.3
+  - @pnpm/lockfile.detect-dep-types@1100.0.24
+  - @pnpm/lockfile.fs@1100.2.8
+  - @pnpm/lockfile.types@1100.1.2
+  - @pnpm/lockfile.utils@1102.1.3
+  - @pnpm/lockfile.walker@1100.0.24
+  - @pnpm/network.fetch@1100.1.17
@@ -0,0 +1,25 @@
+## 1102.1.3
+
+### Patch Changes
+
+- `pnpm audit --interactive --fix=update` no longer opens a second prompt for selecting dependencies to update [#14927](https://github.com/pnpm/pnpm/issues/14927).
+
+- `pnpm sbom` now publishes a valid URL in the CycloneDX `externalReferences[].url` and the SPDX `homepage`. An npm shorthand such as `vercel/ms` or `gitlab:group/subgroup/project` is expanded to the `git+https` URL npm derives for it. An scp-style remote such as `git@github.com:vercel/ms.git` is expanded the same way. Any other URL is published in its normalized form, without embedded credentials. A value that names no repository, an email address for example, is left out. pnpm used to publish the raw value, so a shorthand produced a URL that consumers such as Dependency-Track reject [pnpm/pnpm#14773](https://github.com/pnpm/pnpm/issues/14773).
+
+- Updated dependencies:
+  - @pnpm/cli.utils@1101.0.28
+  - @pnpm/config.reader@1102.2.1
+  - @pnpm/config.writer@1100.0.27
+  - @pnpm/deps.compliance.audit@1101.0.37
+  - @pnpm/deps.compliance.license-scanner@1101.0.5
+  - @pnpm/deps.compliance.sbom@1101.0.4
+  - @pnpm/deps.security.signatures@1102.0.4
+  - @pnpm/installing.commands@1101.3.1
+  - @pnpm/lockfile.fs@1100.2.8
+  - @pnpm/lockfile.types@1100.1.2
+  - @pnpm/lockfile.utils@1102.1.3
+  - @pnpm/lockfile.walker@1100.0.24
+  - @pnpm/network.fetch@1100.1.17
+  - @pnpm/pkg-manifest.utils@1100.4.5
+  - @pnpm/text.sanitize@1100.0.1
+  - @pnpm/workspace.project-manifest-reader@1100.0.29
@@ -0,0 +1,13 @@
+## 1101.0.5
+
+### Patch Changes
+
+- Updated dependencies:
+  - @pnpm/config.package-is-installable@1100.1.7
+  - @pnpm/deps.path@1101.0.3
+  - @pnpm/lockfile.detect-dep-types@1100.0.24
+  - @pnpm/lockfile.fs@1100.2.8
+  - @pnpm/lockfile.types@1100.1.2
+  - @pnpm/lockfile.utils@1102.1.3
+  - @pnpm/lockfile.walker@1100.0.24
+  - @pnpm/store.pkg-finder@1100.0.34
@@ -0,0 +1,16 @@
+## 1101.0.4
+
+### Patch Changes
+
+- `pnpm sbom` now publishes a valid URL in the CycloneDX `externalReferences[].url` and the SPDX `homepage`. An npm shorthand such as `vercel/ms` or `gitlab:group/subgroup/project` is expanded to the `git+https` URL npm derives for it. An scp-style remote such as `git@github.com:vercel/ms.git` is expanded the same way. Any other URL is published in its normalized form, without embedded credentials. A value that names no repository, an email address for example, is left out. pnpm used to publish the raw value, so a shorthand produced a URL that consumers such as Dependency-Track reject [pnpm/pnpm#14773](https://github.com/pnpm/pnpm/issues/14773).
+
+- `pnpm sbom` now emits a license value as a CycloneDX expression only when it is a valid SPDX license expression. Anything else is emitted as a CycloneDX license name [pnpm/pnpm#14786](https://github.com/pnpm/pnpm/issues/14786).
+
+- Updated dependencies:
+  - @pnpm/config.package-is-installable@1100.1.7
+  - @pnpm/lockfile.detect-dep-types@1100.0.24
+  - @pnpm/lockfile.types@1100.1.2
+  - @pnpm/lockfile.utils@1102.1.3
+  - @pnpm/lockfile.walker@1100.0.24
+  - @pnpm/resolving.resolver-base@1101.3.0
+  - @pnpm/store.pkg-finder@1100.0.34
@@ -0,0 +1,6 @@
+## 1100.1.10
+
+### Patch Changes
+
+- Updated dependencies:
+  - @pnpm/resolving.git-resolver@1100.1.22
@@ -0,0 +1,18 @@
+## 1101.0.5
+
+### Patch Changes
+
+- `pnpm install --prod` no longer downloads the registry packages that only a devDependency reaches [#881](https://github.com/pnpm/pnpm/issues/881).
+
+- Updated dependencies:
+  - @pnpm/config.package-is-installable@1100.1.7
+  - @pnpm/core-loggers@1101.0.0
+  - @pnpm/deps.graph-hasher@1100.3.3
+  - @pnpm/deps.path@1101.0.3
+  - @pnpm/fs.symlink-dependency@1100.0.20
+  - @pnpm/hooks.types@1101.0.3
+  - @pnpm/installing.modules-yaml@1101.0.3
+  - @pnpm/lockfile.fs@1100.2.8
+  - @pnpm/lockfile.utils@1102.1.3
+  - @pnpm/patching.config@1100.1.6
+  - @pnpm/store.controller-types@1101.3.0
@@ -0,0 +1,9 @@
+## 1100.3.3
+
+### Patch Changes
+
+- Updated dependencies:
+  - @pnpm/deps.path@1101.0.3
+  - @pnpm/lockfile.types@1100.1.2
+  - @pnpm/lockfile.utils@1102.1.3
+  - @pnpm/resolving.resolver-base@1101.3.0
@@ -0,0 +1,38 @@
+## 1101.0.5
+
+### Patch Changes
+
+- Install warnings no longer carry the text of a package's deprecation notice. The warning names the deprecated package and version, and the `pnpm:deprecation` event no longer carries the notice either. `pnpm view` still shows it on request.
+
+  A deprecation warning now names the newest version of the package that is not deprecated, and says when reaching it means widening the range you declared:
+
+  ```
+  WARN  deprecated foo@1.0.0. 2.3.1 is not deprecated, outside the range you declared.
+  ```
+
+  pnpm works this out from the metadata it already fetched, so it costs no extra request. An install that reuses the lockfile without fetching metadata names no version.
+
+  pnpm strips control characters from the package name and version in a deprecation warning, and from the notice `pnpm outdated --long` prints.
+
+  The text sanitizer now also strips the Unicode line and paragraph separators U+2028 and U+2029.
+
+- `pnpm -r list --json` now prints one JSON array. It printed a separate array for each project when `sharedWorkspaceLockfile` was `false`, so the output could not be parsed.
+
+  `pnpm -r list` now reads each project's own modules directory when the projects keep their own lockfiles, so `--long` and `--parseable` report the packages that project installed [#15011](https://github.com/pnpm/pnpm/issues/15011).
+
+- Updated dependencies:
+  - @pnpm/cli.utils@1101.0.28
+  - @pnpm/config.reader@1102.2.1
+  - @pnpm/deps.github-actions@1100.1.10
+  - @pnpm/deps.inspection.list@1101.0.5
+  - @pnpm/deps.inspection.outdated@1100.1.31
+  - @pnpm/deps.inspection.peers-checker@1100.0.34
+  - @pnpm/global.commands@1102.0.2
+  - @pnpm/global.packages@1101.1.3
+  - @pnpm/installing.modules-yaml@1101.0.3
+  - @pnpm/lockfile.fs@1100.2.8
+  - @pnpm/network.fetch@1100.1.17
+  - @pnpm/resolving.default-resolver@1101.0.5
+  - @pnpm/resolving.npm-resolver@1104.2.0
+  - @pnpm/text.sanitize@1100.0.1
+  - @pnpm/workspace.project-manifest-reader@1100.0.29
@@ -0,0 +1,12 @@
+## 1101.0.5
+
+### Patch Changes
+
+- `pnpm -r list --json` now prints one JSON array. It printed a separate array for each project when `sharedWorkspaceLockfile` was `false`, so the output could not be parsed.
+
+  `pnpm -r list` now reads each project's own modules directory when the projects keep their own lockfiles, so `--long` and `--parseable` report the packages that project installed [#15011](https://github.com/pnpm/pnpm/issues/15011).
+
+- Updated dependencies:
+  - @pnpm/deps.inspection.tree-builder@1101.0.5
+  - @pnpm/lockfile.fs@1100.2.8
+  - @pnpm/workspace.project-manifest-reader@1100.0.29
@@ -0,0 +1,12 @@
+## 1100.1.31
+
+### Patch Changes
+
+- Updated dependencies:
+  - @pnpm/deps.path@1101.0.3
+  - @pnpm/hooks.read-package-hook@1100.3.3
+  - @pnpm/installing.client@1100.3.10
+  - @pnpm/lockfile.fs@1100.2.8
+  - @pnpm/lockfile.utils@1102.1.3
+  - @pnpm/pkg-manifest.utils@1100.4.5
+  - @pnpm/resolving.npm-resolver@1104.2.0
@@ -0,0 +1,8 @@
+## 1100.0.34
+
+### Patch Changes
+
+- Updated dependencies:
+  - @pnpm/deps.path@1101.0.3
+  - @pnpm/lockfile.fs@1100.2.8
+  - @pnpm/lockfile.walker@1100.0.24
@@ -0,0 +1,11 @@
+## 1101.0.5
+
+### Patch Changes
+
+- Updated dependencies:
+  - @pnpm/deps.path@1101.0.3
+  - @pnpm/installing.modules-yaml@1101.0.3
+  - @pnpm/lockfile.detect-dep-types@1100.0.24
+  - @pnpm/lockfile.fs@1100.2.8
+  - @pnpm/lockfile.utils@1102.1.3
+  - @pnpm/store.cafs@1100.3.3
@@ -0,0 +1,6 @@
+## 1101.0.3
+
+### Patch Changes
+
+- Updated dependencies:
+  - @pnpm/crypto.hash@1100.0.5
@@ -0,0 +1,6 @@
+## 1102.0.4
+
+### Patch Changes
+
+- Updated dependencies:
+  - @pnpm/network.fetch@1100.1.17
@@ -0,0 +1,15 @@
+## 1100.1.23
+
+### Patch Changes
+
+- `pnpm install` now returns "Already up to date" in a workspace where `dedupeDirectDeps` left a project without a `node_modules` directory of its own. Such a project forced a full install on every run.
+
+- Updated dependencies:
+  - @pnpm/config.reader@1102.2.1
+  - @pnpm/installing.context@1101.0.5
+  - @pnpm/lockfile.fs@1100.2.8
+  - @pnpm/lockfile.settings-checker@1100.2.7
+  - @pnpm/lockfile.verification@1100.1.6
+  - @pnpm/resolving.resolver-base@1101.3.0
+  - @pnpm/workspace.projects-reader@1101.0.28
+  - @pnpm/workspace.state@1100.0.44
@@ -0,0 +1,27 @@
+## 1102.1.3
+
+### Patch Changes
+
+- `pn`, `pnpx`, and `pnx` now run the pnpm installed alongside them. They used to look pnpm up on `PATH`. That failed when the directory holding them was not on `PATH`, and it silently handed the call to an unrelated pnpm when one came first there [#14803](https://github.com/pnpm/pnpm/issues/14803).
+
+- `pnpm setup` now describes the displayed configuration changes as "the following configuration changes."
+
+- Updated dependencies:
+  - @pnpm/bins.linker@1100.0.32
+  - @pnpm/building.policy@1100.1.2
+  - @pnpm/cli.utils@1101.0.28
+  - @pnpm/config.reader@1102.2.1
+  - @pnpm/deps.graph-hasher@1100.3.3
+  - @pnpm/deps.security.signatures@1102.0.4
+  - @pnpm/global.commands@1102.0.2
+  - @pnpm/global.packages@1101.1.3
+  - @pnpm/installing.client@1100.3.10
+  - @pnpm/installing.deps-restorer@1103.1.3
+  - @pnpm/installing.env-installer@1103.0.5
+  - @pnpm/lockfile.fs@1100.2.8
+  - @pnpm/lockfile.types@1100.1.2
+  - @pnpm/pkg-manifest.utils@1100.4.5
+  - @pnpm/resolving.npm-resolver@1104.2.0
+  - @pnpm/store.connection-manager@1101.1.3
+  - @pnpm/store.controller@1102.1.3
+  - @pnpm/workspace.project-manifest-reader@1100.0.29
@@ -0,0 +1,10 @@
+## 1102.0.21
+
+### Patch Changes
+
+- Updated dependencies:
+  - @pnpm/crypto.shasums-file@1100.2.5
+  - @pnpm/fetching.binary-fetcher@1102.0.15
+  - @pnpm/fetching.fetcher-base@1100.2.10
+  - @pnpm/resolving.npm-resolver@1104.2.0
+  - @pnpm/resolving.resolver-base@1101.3.0
@@ -0,0 +1,10 @@
+## 1101.1.3
+
+### Patch Changes
+
+- Updated dependencies:
+  - @pnpm/cli.utils@1101.0.28
+  - @pnpm/config.reader@1102.2.1
+  - @pnpm/engine.runtime.node-resolver@1101.3.2
+  - @pnpm/exec.pnpm-cli-runner@1100.0.3
+  - @pnpm/network.fetch@1100.1.17
@@ -0,0 +1,10 @@
+## 1102.0.21
+
+### Patch Changes
+
+- Updated dependencies:
+  - @pnpm/crypto.shasums-file@1100.2.5
+  - @pnpm/fetching.binary-fetcher@1102.0.15
+  - @pnpm/fetching.fetcher-base@1100.2.10
+  - @pnpm/resolving.npm-resolver@1104.2.0
+  - @pnpm/resolving.resolver-base@1101.3.0
@@ -0,0 +1,10 @@
+## 1101.3.2
+
+### Patch Changes
+
+- Resolving a Node.js runtime now fails when unofficial-builds.nodejs.org cannot be reached. pnpm used to ignore that failure and leave the musl builds out of `pnpm-lock.yaml`. `pnpm update` then wrote a different lockfile on a machine whose network blocks the mirror [pnpm/pnpm#14813](https://github.com/pnpm/pnpm/issues/14813).
+
+- Updated dependencies:
+  - @pnpm/config.reader@1102.2.1
+  - @pnpm/crypto.shasums-file@1100.2.5
+  - @pnpm/resolving.resolver-base@1101.3.0
@@ -0,0 +1,14 @@
+## 11.27.1
+
+### Patch Changes
+
+- `pn`, `pnpx`, and `pnx` now run the pnpm installed alongside them. They used to look pnpm up on `PATH`. That failed when the directory holding them was not on `PATH`, and it silently handed the call to an unrelated pnpm when one came first there [#14803](https://github.com/pnpm/pnpm/issues/14803).
+
+- Updated dependencies:
+  - @pnpm/linux-arm64@11.27.1
+  - @pnpm/linux-x64@11.27.1
+  - @pnpm/linuxstatic-arm64@11.27.1
+  - @pnpm/linuxstatic-x64@11.27.1
+  - @pnpm/macos-arm64@11.27.1
+  - @pnpm/win-arm64@11.27.1
+  - @pnpm/win-x64@11.27.1
@@ -0,0 +1,24 @@
+## 1101.1.3
+
+### Patch Changes
+
+- `pnpm exec <command>` and `pnpm <command>` run from a subdirectory of a project now find the executables installed in the project's `node_modules/.bin`. The command still runs in the subdirectory. `PNPM_PACKAGE_NAME` names the project [#5068](https://github.com/pnpm/pnpm/issues/5068).
+
+- `pnpm exec` and `pnpm dlx` now wait for the command to finish shutting down after `Ctrl+C`. A signal sent to pnpm alone now reaches the command, the way it does with `pnpm run`. pnpm used to exit on the interrupt and terminate the command while it was still shutting down [#7374](https://github.com/pnpm/pnpm/issues/7374).
+
+- `pnpm dlx` and `pnx` now prompt to approve dependency build scripts in interactive terminals. Cached packages with pending builds also prompt for approval. Without an interactive terminal, use `--allow-build` to allow the required builds. Fixes [pnpm/pnpm#14943](https://github.com/pnpm/pnpm/issues/14943).
+
+- Updated dependencies:
+  - @pnpm/building.commands@1101.2.3
+  - @pnpm/cli.utils@1101.0.28
+  - @pnpm/config.reader@1102.2.1
+  - @pnpm/core-loggers@1101.0.0
+  - @pnpm/crypto.hash@1100.0.5
+  - @pnpm/deps.status@1100.1.23
+  - @pnpm/engine.runtime.commands@1101.1.3
+  - @pnpm/exec.lifecycle@1100.1.18
+  - @pnpm/exec.pnpm-cli-runner@1100.0.3
+  - @pnpm/installing.client@1100.3.10
+  - @pnpm/installing.commands@1101.3.1
+  - @pnpm/workspace.injected-deps-syncer@1100.0.38
+  - @pnpm/workspace.project-manifest-reader@1100.0.29
@@ -0,0 +1,11 @@
+## 1100.1.18
+
+### Patch Changes
+
+- The `@pnpm/npm-lifecycle` package is now available as `@pnpm/exec.npm-lifecycle`.
+
+- Updated dependencies:
+  - @pnpm/bins.linker@1100.0.32
+  - @pnpm/core-loggers@1101.0.0
+  - @pnpm/fetching.directory-fetcher@1100.0.34
+  - @pnpm/store.controller-types@1101.3.0
@@ -0,0 +1,9 @@
+## 1100.0.0
+
+### Patch Changes
+
+- `pnpm exec` and `pnpm dlx` now wait for the command to finish shutting down after `Ctrl+C`. A signal sent to pnpm alone now reaches the command, the way it does with `pnpm run`. pnpm used to exit on the interrupt and terminate the command while it was still shutting down [#7374](https://github.com/pnpm/pnpm/issues/7374).
+
+- The `@pnpm/npm-lifecycle` package is now available as `@pnpm/exec.npm-lifecycle`.
+
+- A signal sent to pnpm while it runs without a terminal, as a container runtime or a service manager does, now reaches the script even when the shell running it stays the script's parent. pnpm then waits for the script to finish shutting down. Such a signal used to end the shell at once or stay with it, and the script was never told to stop [#7374](https://github.com/pnpm/pnpm/issues/7374).
@@ -0,0 +1,5 @@
+## 1100.0.3
+
+### Patch Changes
+
+- `pnpm runtime set` and `pnpm env use` now use the pnpm version that started the command. They could run a different installed pnpm when the command was started through Corepack or another wrapper.
@@ -0,0 +1,8 @@
+## 1100.0.37
+
+### Patch Changes
+
+- `pnpm install` now installs git-hosted dependencies without preparing them when their builds are explicitly denied by `allowBuilds`. Dependencies that require preparation still need an explicit allow or deny decision [pnpm/pnpm#10522](https://github.com/pnpm/pnpm/issues/10522).
+
+- Updated dependencies:
+  - @pnpm/exec.lifecycle@1100.1.18
@@ -0,0 +1,6 @@
+## 1102.0.15
+
+### Patch Changes
+
+- Updated dependencies:
+  - @pnpm/fetching.fetcher-base@1100.2.10
@@ -0,0 +1,8 @@
+## 1100.0.34
+
+### Patch Changes
+
+- Updated dependencies:
+  - @pnpm/fetching.fetcher-base@1100.2.10
+  - @pnpm/resolving.resolver-base@1101.3.0
+  - @pnpm/workspace.project-manifest-reader@1100.0.29
@@ -0,0 +1,8 @@
+## 1100.2.10
+
+### Patch Changes
+
+- `pnpm install` now installs git-hosted dependencies without preparing them when their builds are explicitly denied by `allowBuilds`. Dependencies that require preparation still need an explicit allow or deny decision [pnpm/pnpm#10522](https://github.com/pnpm/pnpm/issues/10522).
+
+- Updated dependencies:
+  - @pnpm/resolving.resolver-base@1101.3.0
@@ -0,0 +1,10 @@
+## 1102.0.19
+
+### Patch Changes
+
+- `pnpm install` now installs git-hosted dependencies without preparing them when their builds are explicitly denied by `allowBuilds`. Dependencies that require preparation still need an explicit allow or deny decision [pnpm/pnpm#10522](https://github.com/pnpm/pnpm/issues/10522).
+
+- Updated dependencies:
+  - @pnpm/exec.prepare-package@1100.0.37
+  - @pnpm/fetching.fetcher-base@1100.2.10
+  - @pnpm/resolving.git-resolver@1100.1.22
@@ -0,0 +1,8 @@
+## 1100.1.11
+
+### Patch Changes
+
+- Updated dependencies:
+  - @pnpm/fetching.fetcher-base@1100.2.10
+  - @pnpm/hooks.types@1101.0.3
+  - @pnpm/resolving.resolver-base@1101.3.0
@@ -0,0 +1,11 @@
+## 1102.1.3
+
+### Patch Changes
+
+- `pnpm install` now installs git-hosted dependencies without preparing them when their builds are explicitly denied by `allowBuilds`. Dependencies that require preparation still need an explicit allow or deny decision [pnpm/pnpm#10522](https://github.com/pnpm/pnpm/issues/10522).
+
+- Updated dependencies:
+  - @pnpm/core-loggers@1101.0.0
+  - @pnpm/exec.prepare-package@1100.0.37
+  - @pnpm/fetching.fetcher-base@1100.2.10
+  - @pnpm/fs.graceful-fs@1100.2.2
@@ -0,0 +1,5 @@
+## 1100.2.2
+
+### Patch Changes
+
+- Installs in different projects that share a global virtual store no longer fail on Windows with `Access is denied` while repairing the same slot [#15114](https://github.com/pnpm/pnpm/issues/15114).
@@ -0,0 +1,6 @@
+## 1100.0.6
+
+### Patch Changes
+
+- Updated dependencies:
+  - @pnpm/fs.graceful-fs@1100.2.2
@@ -0,0 +1,10 @@
+## 1100.0.29
+
+### Patch Changes
+
+- Installs in different projects that share a global virtual store no longer fail on Windows with `Access is denied` while repairing the same slot [#15114](https://github.com/pnpm/pnpm/issues/15114).
+
+- Updated dependencies:
+  - @pnpm/core-loggers@1101.0.0
+  - @pnpm/fs.graceful-fs@1100.2.2
+  - @pnpm/store.controller-types@1101.3.0
@@ -0,0 +1,6 @@
+## 1100.0.20
+
+### Patch Changes
+
+- Updated dependencies:
+  - @pnpm/core-loggers@1101.0.0
@@ -3,4 +3,4 @@
 ### Patch Changes

 - Updated dependencies:
-  - @pnpm/releasing.versioning@1100.3.1
+  - @pnpm/releasing.versioning@1100.3.2
@@ -0,0 +1,21 @@
+## 1102.0.2
+
+### Patch Changes
+
+- `pnpm add -g` and `pnpm update -g` now ignore incomplete unrelated global package groups when every command from the replaced group is retained. Operations that could remove a global command still require complete ownership information.
+
+- `pnpm update --global` no longer reinstalls a global package when its dependency graph resolves to what is already installed. It reports `Already up to date` [pnpm/pnpm#12002](https://github.com/pnpm/pnpm/issues/12002).
+
+- Updated dependencies:
+  - @pnpm/bins.linker@1100.0.32
+  - @pnpm/bins.remover@1100.0.24
+  - @pnpm/cli.utils@1101.0.28
+  - @pnpm/config.reader@1102.2.1
+  - @pnpm/core-loggers@1101.0.0
+  - @pnpm/deps.inspection.list@1101.0.5
+  - @pnpm/global.packages@1101.1.3
+  - @pnpm/installing.deps-installer@1104.1.3
+  - @pnpm/installing.modules-yaml@1101.0.3
+  - @pnpm/lockfile.fs@1100.2.8
+  - @pnpm/pkg-manifest.utils@1100.4.5
+  - @pnpm/store.connection-manager@1101.1.3
@@ -0,0 +1,6 @@
+## 1101.1.3
+
+### Patch Changes
+
+- Updated dependencies:
+  - @pnpm/crypto.hash@1100.0.5
@@ -0,0 +1,10 @@
+## 1100.0.32
+
+### Patch Changes
+
+- Updated dependencies:
+  - @pnpm/core-loggers@1101.0.0
+  - @pnpm/crypto.hash@1100.0.5
+  - @pnpm/hooks.types@1101.0.3
+  - @pnpm/lockfile.types@1100.1.2
+  - @pnpm/store.controller-types@1101.3.0
@@ -0,0 +1,8 @@
+## 1100.3.3
+
+### Patch Changes
+
+- pnpm now measures a `pnpm.overrides` entry written as a bare path, such as `./local-dep`, from the directory holding `pnpm-workspace.yaml`. It used to be measured from each package the override rewrote, so the dependency linked to a directory that does not exist [#11131](https://github.com/pnpm/pnpm/issues/11131).
+
+- Updated dependencies:
+  - @pnpm/resolving.local-resolver@1101.2.2
@@ -0,0 +1,8 @@
+## 1101.0.3
+
+### Patch Changes
+
+- Updated dependencies:
+  - @pnpm/fetching.fetcher-base@1100.2.10
+  - @pnpm/lockfile.types@1100.1.2
+  - @pnpm/resolving.resolver-base@1101.3.0
@@ -0,0 +1,15 @@
+## 1100.3.10
+
+### Patch Changes
+
+- Updated dependencies:
+  - @pnpm/engine.runtime.node-resolver@1101.3.2
+  - @pnpm/fetching.binary-fetcher@1102.0.15
+  - @pnpm/fetching.directory-fetcher@1100.0.34
+  - @pnpm/fetching.git-fetcher@1102.0.19
+  - @pnpm/fetching.tarball-fetcher@1102.1.3
+  - @pnpm/hooks.types@1101.0.3
+  - @pnpm/network.fetch@1100.1.17
+  - @pnpm/resolving.default-resolver@1101.0.5
+  - @pnpm/resolving.npm-resolver@1104.2.0
+  - @pnpm/resolving.resolver-base@1101.3.0
@@ -0,0 +1,48 @@
+## 1101.3.1
+
+### Patch Changes
+
+- `pnpm deploy` no longer installs the dependencies of the workspace root project into the deploy directory [#6437](https://github.com/pnpm/pnpm/issues/6437).
+
+- `pnpm install --force` now reinstalls dependencies when the manifest and lockfile are unchanged. It previously reported "Already up to date" without reinstalling. Files changed in `node_modules` are restored when the store content is intact. Combining `--force` with `--frozen-store` now reports a configuration conflict on repeat installs [#919](https://github.com/pnpm/pnpm/issues/919).
+
+- The `minimumReleaseAge` approval prompt now counts and displays each package version once [pnpm/pnpm#15083](https://github.com/pnpm/pnpm/issues/15083).
+
+- Updated dependencies:
+  - @pnpm/building.after-install@1103.0.5
+  - @pnpm/building.policy@1100.1.2
+  - @pnpm/cli.utils@1101.0.28
+  - @pnpm/config.reader@1102.2.1
+  - @pnpm/config.writer@1100.0.27
+  - @pnpm/core-loggers@1101.0.0
+  - @pnpm/deps.github-actions@1100.1.10
+  - @pnpm/deps.inspection.outdated@1100.1.31
+  - @pnpm/deps.path@1101.0.3
+  - @pnpm/deps.security.signatures@1102.0.4
+  - @pnpm/deps.status@1100.1.23
+  - @pnpm/fs.graceful-fs@1100.2.2
+  - @pnpm/global.commands@1102.0.2
+  - @pnpm/global.packages@1101.1.3
+  - @pnpm/hooks.pnpmfile@1100.0.32
+  - @pnpm/installing.context@1101.0.5
+  - @pnpm/installing.dedupe.check@1100.1.13
+  - @pnpm/installing.deps-installer@1104.1.3
+  - @pnpm/installing.env-installer@1103.0.5
+  - @pnpm/lockfile.fs@1100.2.8
+  - @pnpm/lockfile.types@1100.1.2
+  - @pnpm/lockfile.utils@1102.1.3
+  - @pnpm/network.fetch@1100.1.17
+  - @pnpm/pkg-manifest.utils@1100.4.5
+  - @pnpm/resolving.npm-resolver@1104.2.0
+  - @pnpm/resolving.resolver-base@1101.3.0
+  - @pnpm/store.connection-manager@1101.1.3
+  - @pnpm/store.controller@1102.1.3
+  - @pnpm/text.sanitize@1100.0.1
+  - @pnpm/workspace.project-manifest-reader@1100.0.29
+  - @pnpm/workspace.project-manifest-writer@1100.0.17
+  - @pnpm/workspace.projects-filter@1100.0.43
+  - @pnpm/workspace.projects-graph@1100.0.38
+  - @pnpm/workspace.projects-reader@1101.0.28
+  - @pnpm/workspace.root-finder@1100.0.9
+  - @pnpm/workspace.state@1100.0.44
+  - @pnpm/workspace.workspace-manifest-writer@1100.2.1
@@ -0,0 +1,12 @@
+## 1101.0.5
+
+### Patch Changes
+
+- Updated dependencies:
+  - @pnpm/core-loggers@1101.0.0
+  - @pnpm/installing.modules-yaml@1101.0.3
+  - @pnpm/installing.read-projects-context@1101.0.5
+  - @pnpm/lockfile.fs@1100.2.8
+  - @pnpm/lockfile.pruner@1100.0.24
+  - @pnpm/resolving.resolver-base@1101.3.0
+  - @pnpm/store.controller@1102.1.3
@@ -0,0 +1,6 @@
+## 1100.1.13
+
+### Patch Changes
+
+- Updated dependencies:
+  - @pnpm/lockfile.types@1100.1.2
@@ -0,0 +1,50 @@
+## 1104.1.3
+
+### Patch Changes
+
+- Fixed `pnpm dedupe` requiring a second pass after bumping a direct dependency in `package.json` [pnpm/pnpm#14987](https://github.com/pnpm/pnpm/issues/14987).
+
+- `pnpm install --force` now removes obsolete dependency links inside virtual-store packages when their dependencies change. Invalid dependency names are ignored during obsolete-link cleanup [#15039](https://github.com/pnpm/pnpm/issues/15039).
+
+- `pnpm install --prod` no longer downloads the registry packages that only a devDependency reaches [#881](https://github.com/pnpm/pnpm/issues/881).
+
+- `pnpm update` and `pnpm audit --fix=update` no longer copy dependencies added by `packageExtensions`, a `readPackage` hook, or an override into `package.json`. Those dependencies keep the specifier the hook or override gives them. `pnpm update --latest` no longer resolves past that specifier. `pnpm audit --fix=update` now warns when one of them pins a vulnerable version. The warning points at `pnpm audit --fix` [#14928](https://github.com/pnpm/pnpm/issues/14928).
+
+- Updated dependencies:
+  - @pnpm/bins.linker@1100.0.32
+  - @pnpm/bins.remover@1100.0.24
+  - @pnpm/building.after-install@1103.0.5
+  - @pnpm/building.during-install@1102.2.2
+  - @pnpm/building.policy@1100.1.2
+  - @pnpm/core-loggers@1101.0.0
+  - @pnpm/crypto.hash@1100.0.5
+  - @pnpm/deps.graph-hasher@1100.3.3
+  - @pnpm/deps.path@1101.0.3
+  - @pnpm/exec.lifecycle@1100.1.18
+  - @pnpm/fs.symlink-dependency@1100.0.20
+  - @pnpm/hooks.read-package-hook@1100.3.3
+  - @pnpm/hooks.types@1101.0.3
+  - @pnpm/installing.context@1101.0.5
+  - @pnpm/installing.deps-resolver@1102.2.2
+  - @pnpm/installing.deps-restorer@1103.1.3
+  - @pnpm/installing.linking.direct-dep-linker@1100.0.20
+  - @pnpm/installing.linking.hoist@1100.0.32
+  - @pnpm/installing.linking.modules-cleaner@1100.1.24
+  - @pnpm/installing.modules-yaml@1101.0.3
+  - @pnpm/installing.package-requester@1102.1.15
+  - @pnpm/lockfile.filtering@1100.2.8
+  - @pnpm/lockfile.fs@1100.2.8
+  - @pnpm/lockfile.preferred-versions@1100.0.34
+  - @pnpm/lockfile.pruner@1100.0.24
+  - @pnpm/lockfile.settings-checker@1100.2.7
+  - @pnpm/lockfile.to-pnp@1101.0.5
+  - @pnpm/lockfile.utils@1102.1.3
+  - @pnpm/lockfile.verification@1100.1.6
+  - @pnpm/lockfile.walker@1100.0.24
+  - @pnpm/patching.config@1100.1.6
+  - @pnpm/pkg-manifest.utils@1100.4.5
+  - @pnpm/pnpr.client@3.0.3
+  - @pnpm/resolving.local-resolver@1101.2.2
+  - @pnpm/resolving.resolver-base@1101.3.0
+  - @pnpm/store.controller-types@1101.3.0
+  - @pnpm/workspace.project-manifest-reader@1100.0.29
@@ -0,0 +1,40 @@
+## 1102.2.2
+
+### Patch Changes
+
+- Install warnings no longer carry the text of a package's deprecation notice. The warning names the deprecated package and version, and the `pnpm:deprecation` event no longer carries the notice either. `pnpm view` still shows it on request.
+
+  A deprecation warning now names the newest version of the package that is not deprecated, and says when reaching it means widening the range you declared:
+
+  ```
+  WARN  deprecated foo@1.0.0. 2.3.1 is not deprecated, outside the range you declared.
+  ```
+
+  pnpm works this out from the metadata it already fetched, so it costs no extra request. An install that reuses the lockfile without fetching metadata names no version.
+
+  pnpm strips control characters from the package name and version in a deprecation warning, and from the notice `pnpm outdated --long` prints.
+
+  The text sanitizer now also strips the Unicode line and paragraph separators U+2028 and U+2029.
+
+- pnpm now deduplicates a package whose child dependency resolved an optional peer in one workspace project but not in another. Two copies of `next` could appear when only some projects could reach `styled-jsx`'s optional `babel-plugin-macros` peer [#14800](https://github.com/pnpm/pnpm/issues/14800).
+
+- `pnpm install --prod` no longer downloads the registry packages that only a devDependency reaches [#881](https://github.com/pnpm/pnpm/issues/881).
+
+- `pnpm update` and `pnpm audit --fix=update` no longer copy dependencies added by `packageExtensions`, a `readPackage` hook, or an override into `package.json`. Those dependencies keep the specifier the hook or override gives them. `pnpm update --latest` no longer resolves past that specifier. `pnpm audit --fix=update` now warns when one of them pins a vulnerable version. The warning points at `pnpm audit --fix` [#14928](https://github.com/pnpm/pnpm/issues/14928).
+
+- Updated dependencies:
+  - @pnpm/core-loggers@1101.0.0
+  - @pnpm/deps.graph-hasher@1100.3.3
+  - @pnpm/deps.path@1101.0.3
+  - @pnpm/fetching.pick-fetcher@1100.1.11
+  - @pnpm/fs.symlink-dependency@1100.0.20
+  - @pnpm/hooks.types@1101.0.3
+  - @pnpm/lockfile.preferred-versions@1100.0.34
+  - @pnpm/lockfile.pruner@1100.0.24
+  - @pnpm/lockfile.types@1100.1.2
+  - @pnpm/lockfile.utils@1102.1.3
+  - @pnpm/patching.config@1100.1.6
+  - @pnpm/pkg-manifest.utils@1100.4.5
+  - @pnpm/resolving.npm-resolver@1104.2.0
+  - @pnpm/resolving.resolver-base@1101.3.0
+  - @pnpm/store.controller-types@1101.3.0
@@ -0,0 +1,35 @@
+## 1103.1.3
+
+### Patch Changes
+
+- `pnpm install --force` now removes obsolete dependency links inside virtual-store packages when their dependencies change. Invalid dependency names are ignored during obsolete-link cleanup [#15039](https://github.com/pnpm/pnpm/issues/15039).
+
+- The install summary now names the version each dependency resolved to when `node-linker` is `hoisted`. It also lists what an install restores after `node_modules` is deleted, and both sides of a version change. The summary showed the range recorded in `package.json`, or nothing at all [#15161](https://github.com/pnpm/pnpm/issues/15161).
+
+- `pnpm install --prod` no longer downloads the registry packages that only a devDependency reaches [#881](https://github.com/pnpm/pnpm/issues/881).
+
+- Updated dependencies:
+  - @pnpm/bins.linker@1100.0.32
+  - @pnpm/building.during-install@1102.2.2
+  - @pnpm/building.policy@1100.1.2
+  - @pnpm/config.package-is-installable@1100.1.7
+  - @pnpm/core-loggers@1101.0.0
+  - @pnpm/deps.graph-builder@1101.0.5
+  - @pnpm/deps.graph-hasher@1100.3.3
+  - @pnpm/deps.path@1101.0.3
+  - @pnpm/exec.lifecycle@1100.1.18
+  - @pnpm/fs.symlink-dependency@1100.0.20
+  - @pnpm/installing.linking.direct-dep-linker@1100.0.20
+  - @pnpm/installing.linking.hoist@1100.0.32
+  - @pnpm/installing.linking.modules-cleaner@1100.1.24
+  - @pnpm/installing.linking.real-hoist@1100.1.19
+  - @pnpm/installing.modules-yaml@1101.0.3
+  - @pnpm/installing.package-requester@1102.1.15
+  - @pnpm/lockfile.filtering@1100.2.8
+  - @pnpm/lockfile.fs@1100.2.8
+  - @pnpm/lockfile.to-pnp@1101.0.5
+  - @pnpm/lockfile.utils@1102.1.3
+  - @pnpm/patching.config@1100.1.6
+  - @pnpm/pnpr.client@3.0.3
+  - @pnpm/store.controller-types@1101.3.0
+  - @pnpm/workspace.project-manifest-reader@1100.0.29
@@ -0,0 +1,20 @@
+## 1103.0.5
+
+### Patch Changes
+
+- Updated dependencies:
+  - @pnpm/config.package-is-installable@1100.1.7
+  - @pnpm/config.writer@1100.0.27
+  - @pnpm/core-loggers@1101.0.0
+  - @pnpm/deps.graph-hasher@1100.3.3
+  - @pnpm/deps.path@1101.0.3
+  - @pnpm/fs.symlink-dependency@1100.0.20
+  - @pnpm/installing.deps-resolver@1102.2.2
+  - @pnpm/lockfile.fs@1100.2.8
+  - @pnpm/lockfile.pruner@1100.0.24
+  - @pnpm/lockfile.types@1100.1.2
+  - @pnpm/lockfile.utils@1102.1.3
+  - @pnpm/network.fetch@1100.1.17
+  - @pnpm/resolving.npm-resolver@1104.2.0
+  - @pnpm/store.controller@1102.1.3
+  - @pnpm/store.controller-types@1101.3.0
@@ -0,0 +1,7 @@
+## 1100.0.20
+
+### Patch Changes
+
+- Updated dependencies:
+  - @pnpm/core-loggers@1101.0.0
+  - @pnpm/fs.symlink-dependency@1100.0.20
@@ -0,0 +1,7 @@
+## 1100.0.32
+
+### Patch Changes
+
+- Updated dependencies:
+  - @pnpm/bins.linker@1100.0.32
+  - @pnpm/core-loggers@1101.0.0
@@ -0,0 +1,12 @@
+## 1100.1.24
+
+### Patch Changes
+
+- Updated dependencies:
+  - @pnpm/bins.remover@1100.0.24
+  - @pnpm/core-loggers@1101.0.0
+  - @pnpm/deps.path@1101.0.3
+  - @pnpm/lockfile.filtering@1100.2.8
+  - @pnpm/lockfile.types@1100.1.2
+  - @pnpm/lockfile.utils@1102.1.3
+  - @pnpm/store.controller-types@1101.3.0
@@ -0,0 +1,8 @@
+## 1100.1.19
+
+### Patch Changes
+
+- Updated dependencies:
+  - @pnpm/deps.path@1101.0.3
+  - @pnpm/lockfile.types@1100.1.2
+  - @pnpm/lockfile.utils@1102.1.3
@@ -0,0 +1,6 @@
+## 1101.0.3
+
+### Patch Changes
+
+- Updated dependencies:
+  - @pnpm/fs.graceful-fs@1100.2.2
@@ -0,0 +1,32 @@
+## 1102.1.15
+
+### Patch Changes
+
+- Install warnings no longer carry the text of a package's deprecation notice. The warning names the deprecated package and version, and the `pnpm:deprecation` event no longer carries the notice either. `pnpm view` still shows it on request.
+
+  A deprecation warning now names the newest version of the package that is not deprecated, and says when reaching it means widening the range you declared:
+
+  ```
+  WARN  deprecated foo@1.0.0. 2.3.1 is not deprecated, outside the range you declared.
+  ```
+
+  pnpm works this out from the metadata it already fetched, so it costs no extra request. An install that reuses the lockfile without fetching metadata names no version.
+
+  pnpm strips control characters from the package name and version in a deprecation warning, and from the notice `pnpm outdated --long` prints.
+
+  The text sanitizer now also strips the Unicode line and paragraph separators U+2028 and U+2029.
+
+- `pnpm install` now installs git-hosted dependencies without preparing them when their builds are explicitly denied by `allowBuilds`. Dependencies that require preparation still need an explicit allow or deny decision [pnpm/pnpm#10522](https://github.com/pnpm/pnpm/issues/10522).
+
+- Updated dependencies:
+  - @pnpm/config.package-is-installable@1100.1.7
+  - @pnpm/core-loggers@1101.0.0
+  - @pnpm/deps.path@1101.0.3
+  - @pnpm/exec.prepare-package@1100.0.37
+  - @pnpm/fetching.fetcher-base@1100.2.10
+  - @pnpm/fetching.pick-fetcher@1100.1.11
+  - @pnpm/fs.graceful-fs@1100.2.2
+  - @pnpm/hooks.types@1101.0.3
+  - @pnpm/resolving.resolver-base@1101.3.0
+  - @pnpm/store.cafs@1100.3.3
+  - @pnpm/store.controller-types@1101.3.0
@@ -0,0 +1,7 @@
+## 1101.0.5
+
+### Patch Changes
+
+- Updated dependencies:
+  - @pnpm/installing.modules-yaml@1101.0.3
+  - @pnpm/lockfile.fs@1100.2.8
@@ -3,4 +3,4 @@
 ### Patch Changes

 - Updated dependencies:
-  - @pnpm/worker@1100.4.2
+  - @pnpm/worker@1100.4.3
@@ -0,0 +1 @@
+## 11.27.1
@@ -0,0 +1 @@
+## 11.27.1
@@ -0,0 +1 @@
+## 11.27.1
@@ -0,0 +1 @@
+## 11.27.1
@@ -0,0 +1,7 @@
+## 1100.0.24
+
+### Patch Changes
+
+- Updated dependencies:
+  - @pnpm/deps.path@1101.0.3
+  - @pnpm/lockfile.types@1100.1.2
@@ -0,0 +1,10 @@
+## 1100.2.8
+
+### Patch Changes
+
+- Updated dependencies:
+  - @pnpm/config.package-is-installable@1100.1.7
+  - @pnpm/deps.path@1101.0.3
+  - @pnpm/lockfile.types@1100.1.2
+  - @pnpm/lockfile.utils@1102.1.3
+  - @pnpm/lockfile.walker@1100.0.24
@@ -0,0 +1,10 @@
+## 1100.2.8
+
+### Patch Changes
+
+- Updated dependencies:
+  - @pnpm/deps.path@1101.0.3
+  - @pnpm/lockfile.merger@1100.0.23
+  - @pnpm/lockfile.types@1100.1.2
+  - @pnpm/lockfile.utils@1102.1.3
+  - @pnpm/network.git-utils@1100.0.4
@@ -0,0 +1,10 @@
+## 1100.0.41
+
+### Patch Changes
+
+- Updated dependencies:
+  - @pnpm/lockfile.fs@1100.2.8
+  - @pnpm/lockfile.pruner@1100.0.24
+  - @pnpm/releasing.exportable-manifest@1100.3.2
+  - @pnpm/workspace.project-manifest-reader@1100.0.29
+  - @pnpm/workspace.root-finder@1100.0.9
@@ -0,0 +1,6 @@
+## 1100.0.23
+
+### Patch Changes
+
+- Updated dependencies:
+  - @pnpm/lockfile.types@1100.1.2
@@ -0,0 +1,10 @@
+## 1100.0.34
+
+### Patch Changes
+
+- Fixed `pnpm dedupe` requiring a second pass after bumping a direct dependency in `package.json` [pnpm/pnpm#14987](https://github.com/pnpm/pnpm/issues/14987).
+
+- Updated dependencies:
+  - @pnpm/lockfile.utils@1102.1.3
+  - @pnpm/pkg-manifest.utils@1100.4.5
+  - @pnpm/resolving.resolver-base@1101.3.0
@@ -0,0 +1,7 @@
+## 1100.0.24
+
+### Patch Changes
+
+- Updated dependencies:
+  - @pnpm/deps.path@1101.0.3
+  - @pnpm/lockfile.types@1100.1.2
@@ -0,0 +1,8 @@
+## 1100.2.7
+
+### Patch Changes
+
+- Updated dependencies:
+  - @pnpm/crypto.hash@1100.0.5
+  - @pnpm/lockfile.types@1100.1.2
+  - @pnpm/lockfile.verification@1100.1.6
@@ -0,0 +1,9 @@
+## 1101.0.5
+
+### Patch Changes
+
+- Updated dependencies:
+  - @pnpm/deps.path@1101.0.3
+  - @pnpm/fs.symlink-dependency@1100.0.20
+  - @pnpm/lockfile.fs@1100.2.8
+  - @pnpm/lockfile.utils@1102.1.3
@@ -0,0 +1,6 @@
+## 1100.1.2
+
+### Patch Changes
+
+- Updated dependencies:
+  - @pnpm/resolving.resolver-base@1101.3.0
@@ -0,0 +1,9 @@
+## 1102.1.3
+
+### Patch Changes
+
+- Updated dependencies:
+  - @pnpm/deps.path@1101.0.3
+  - @pnpm/hooks.types@1101.0.3
+  - @pnpm/lockfile.types@1100.1.2
+  - @pnpm/resolving.resolver-base@1101.3.0
@@ -0,0 +1,11 @@
+## 1100.1.6
+
+### Patch Changes
+
+- Updated dependencies:
+  - @pnpm/crypto.hash@1100.0.5
+  - @pnpm/deps.path@1101.0.3
+  - @pnpm/installing.context@1101.0.5
+  - @pnpm/lockfile.types@1100.1.2
+  - @pnpm/lockfile.utils@1102.1.3
+  - @pnpm/resolving.resolver-base@1101.3.0
@@ -0,0 +1,7 @@
+## 1100.0.24
+
+### Patch Changes
+
+- Updated dependencies:
+  - @pnpm/deps.path@1101.0.3
+  - @pnpm/lockfile.types@1100.1.2
@@ -0,0 +1 @@
+## 11.27.1
@@ -0,0 +1,10 @@
+## 1100.0.44
+
+### Patch Changes
+
+- Updated dependencies:
+  - @pnpm/config.reader@1102.2.1
+  - @pnpm/deps.path@1101.0.3
+  - @pnpm/lockfile.fs@1100.2.8
+  - @pnpm/lockfile.utils@1102.1.3
+  - @pnpm/store.cafs@1100.3.3