Bump pnpm from 9.15.5 to 10.2.0

[dependabot]

Bumps pnpm from 9.15.5 to 10.2.0.

Release notes

Sourced from pnpm's releases.

pnpm 10.2

See breaking changes in v10

Minor Changes

• Packages executed via pnpm dlx and pnpm create are allowed to be built (run postinstall scripts) by default.

  If the packages executed by dlx or create have dependencies that have to be built, they should be listed via the --allow-build flag. For instance, if you want to run a package called bundle that has esbuild in dependencies and want to allow esbuild to run postinstall scripts, run:

  pnpm --allow-build=esbuild dlx bundle
  

  Related PR: #9026.

Patch Changes

• Quote args for scripts with shell-quote to support new lines (on POSIX only) #8980.
• Fix a bug in which pnpm deploy fails to read the correct projectId when the deploy source is the same as the workspace directory #9001.
• Proxy settings should be respected, when resolving Git-hosted dependencies #6530.
• Prevent overrides from adding invalid version ranges to peerDependencies by keeping the peerDependencies and overriding them with prod dependencies #8978.
• Sort the package names in the "pnpm.onlyBuiltDependencies" list saved by pnpm approve-builds.

Platinum Sponsors

Gold Sponsors

... (truncated)

Changelog

Sourced from pnpm's changelog.

10.2.0

Minor Changes

• Packages executed via pnpm dlx and pnpm create are allowed to be built (run postinstall scripts) by default.

  If the packages executed by dlx or create have dependencies that have to be built, they should be listed via the --allow-build flag. For instance, if you want to run a package called bundle that has esbuild in dependencies and want to allow esbuild to run postinstall scripts, run:

  pnpm --allow-build=esbuild dlx bundle
  

  Related PR: #9026.

Patch Changes

• Quote args for scripts with shell-quote to support new lines (on POSIX only) #8980.
• Fix a bug in which pnpm deploy fails to read the correct projectId when the deploy source is the same as the workspace directory #9001.
• Proxy settings should be respected, when resolving Git-hosted dependencies #6530.
• Prevent overrides from adding invalid version ranges to peerDependencies by keeping the peerDependencies and overriding them with prod dependencies #8978.
• Sort the package names in the "pnpm.onlyBuiltDependencies" list saved by pnpm approve-builds.

10.1.0

Minor Changes

• Added a new command for printing the list of dependencies with ignored build scripts: pnpm ignored-builds #8963.
• Added a new command for approving dependencies for running scripts during installation: pnpm approve-builds #8963.
• Added a new setting called optimistic-repeat-install. When enabled, a fast check will be performed before proceeding to installation. This way a repeat install or an install on a project with everything up-to-date becomes a lot faster. But some edge cases might arise, so we keep it disabled by default for now #8977.
• Added a new field "pnpm.ignoredBuiltDependencies" for explicitly listing packages that should not be built. When a package is in the list, pnpm will not print an info message about that package not being built #8935.

Patch Changes

• Verify that the package name is valid when executing the publish command.
• When running pnpm install, the preprepare and postprepare scripts of the project should be executed #8989.
• Allow workspace: and catalog: to be part of wider version range in peerDependencies.
• pnpm deploy should inherit the pnpm object from the root package.json #8991.
• Make sure that the deletion of a node_modules in a sub-project of a monorepo is detected as out-of-date #8959.
• Fix infinite loop caused by lifecycle scripts using pnpm to execute other scripts during pnpm install with verify-deps-before-run=install #8954.
• Replace strip-ansi with the built-in util.stripVTControlCharacters #9009.
• Do not print patched dependencies as ignored dependencies that require a build #8952.

10.0.0

Major Changes

• Lifecycle scripts of dependencies are not executed during installation by default! This is a breaking change aimed at increasing security. In order to allow lifecycle scripts of specific dependencies, they should be listed in the pnpm.onlyBuiltDependencies field of package.json #8897. For example:

  {

... (truncated)

Commits

• 97e0f5d chore(release): 10.2.0
• c0d1c01 fix(lifecycle): properly quote args (#9018)
• c5a0b9e chore(release): 10.1.0
• 0858c06 test: add tests for pnpm rebuild in deployed packages (#8990)
• acdf26d refactor: replace strip-ansi with built-in util.stripVTControlCharacters ...
• 5c8654f fix: check for delete modules dir in sub-project (#8967)
• 961dc5d feat: add ignored-builds command (#8963)
• c96eb2b fix(lifecycle): skip verify for install hooks (#8957)
• 42ecf04 chore(release): 10.0.0
• c0c63ef docs: update years
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)