chore(deps): update pnpm to v9.1.1

[app-token-issuer-releng-renovate]

This PR contains the following updates:

Package	Type	Update	Change
pnpm (source)	engines	major	8 -> 9
pnpm (source)		minor	9.0.5 -> 9.1.1

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

Release Notes

pnpm/pnpm (pnpm)

v9.1.1

Compare Source

Patch Changes

• Improve the performance of the peers resolution stage by utilizing more cache #​8058.
• Overrides with link: now preserve absolute path #​8053.
• Fix incorrect path when resolving relative file: overrides for workspace package #​8053.
• Print a better error message when resolution-mode is set to time-based and the registry fails to return the "time" field in the package's metadata.
• Fix shell completion on MinGW-w64 environment.

Platinum Sponsors

Gold Sponsors

Our Silver Sponsors

v9.1.0

Compare Source

Minor Changes

• New setting called virtual-store-dir-max-length added to modify the maximum allowed length of the directories inside node_modules/.pnpm. The default length is set to 120 characters. This setting is particularly useful on Windows, where there is a limit to the maximum length of a file path #​7355.

Patch Changes

• A dependency is hoisted to resolve an optional peer dependency only if it satisfies the range provided for the optional peer dependency #​8028.
• Details in the pnpm outdated output are wrapped correctly #​8037.
• Fix Cannot read properties of undefined (reading 'missingPeersOfChildren') exception that happens on install #​8041.
• Explicitly throw an error when user attempts to run publish or pack when bundledDependencies is set but node-linker isn't hoisted.
• pnpm update should not fail when there's an aliased local workspace dependency #​7975.

Platinum Sponsors

Gold Sponsors

Our Silver Sponsors

v9.0.6

Compare Source

Patch Changes

• Lockfiles that have git-hosted dependencies specified should be correctly converted to the new lockfile format #​7990.
• Don't upgrade the lockfile format on pnpm install --frozen-lockfile #​7991.

Platinum Sponsors

Gold Sponsors

Our Silver Sponsors

v9.0.5

Compare Source

Patch Changes

• Lockfiles with local or git-hosted dependencies are now successfully converted to the new lockfile format #​7955.
• Resolve peer dependencies correctly, when they have prerelease versions #​7977.
• Fix aliased dependencies resolution on repeat install with existing lockfile, when the aliased dependency doesn't specify a version or range #​7957.
• The lockfile should be saved in the new format even if it is up-to-date.

Platinum Sponsors

Gold Sponsors

Our Silver Sponsors

v9.0.4

Compare Source

Patch Changes

• Fix aliased dependencies resolution on repeat install with existing lockfile #​7957.
• The engines.pnpm field in the package.json files of dependencies should be ignored #​7965.

Platinum Sponsors

Gold Sponsors

Our Silver Sponsors

v9.0.3

Compare Source

Patch Changes

• If the script-shell option is configured to a .bat/.cmd file on Windows, pnpm will now error with ERR_PNPM_INVALID_SCRIPT_SHELL_WINDOWS. Newer versions of Node.js released in April 2024 do not support executing these files directly without behavior differences. If the script-shell option is necessary for your use-case, please set a .exe file instead.
• Print a hint about the package-manager-strict setting, when pnpm doesn't match the version specified in the packageManager field in package.json.
• pnpm completion command should work in the standalone version of pnpm #​7948.

Platinum Sponsors

Gold Sponsors

Our Silver Sponsors

v9.0.2

Compare Source

Patch Changes

• Fixed an issue where optional dependencies were not linked into the dependent's node_modules #​7943.

Platinum Sponsors

Gold Sponsors

Our Silver Sponsors

v9.0.1

Compare Source

Patch Changes

• pnpm install --frozen-lockfile should work with lockfiles generated by pnpm v8, if they don't need updates #​7934.

Platinum Sponsors

Gold Sponsors

Renovate Bot.

[app-token-issuer-releng-renovate]

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 9.x releases. But if you manually upgrade to 9.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.