v10.5.2

Compare Source

Patch Changes

• The pnpm config set command should change the global .npmrc file by default.
  This was a regression introduced by #​9151 and shipped in pnpm v10.5.0.

v10.5.1

Compare Source

Patch Changes

• Throw an error message if a pnpm-workspaces.yaml or pnpm-workspaces.yml file is found instead of a pnpm-workspace.yaml #​9170.
• Fix the update of pnpm-workspace.yaml by the pnpm approve-builds command #​9168.
• Normalize generated link paths in package.json #​9163
• Specifying overrides in pnpm-workspace.yaml should work.
• pnpm dlx should ignore settings from the package.json file in the current working directory #​9178.

v10.5.0

Compare Source

Minor Changes

• Allow to set the "pnpm" settings from package.json via the pnpm-workspace.yaml file #​9121.

• Added support for automatically syncing files of injected workspace packages after pnpm run #​9081. Use the sync-injected-deps-after-scripts setting to specify which scripts build the workspace package. This tells pnpm when syncing is needed. The setting should be defined in a .npmrc file at the root of the workspace. Example:

  sync-injected-deps-after-scripts[]=compile

• The packages field in pnpm-workspace.yaml became optional.

Patch Changes

• pnpm link with no parameters should work as if --global is specified #​9151.
• Allow scope registry CLI option without --config. prefix such as --@​scope:registry=https://scope.example.com/npm #​9089.
• pnpm link <path> should calculate relative path from the root of the workspace directory #​9132.
• Fix a bug causing catalog snapshots to be removed from the pnpm-lock.yaml file when using --fix-lockfile and --filter. #​8639
• Fix a bug causing catalog protocol dependencies to not re-resolve on a filtered install #​8638.