pnpm/pnpm (pnpm)
### [`v9.7.0`](https://togithub.com/pnpm/pnpm/releases/tag/v9.7.0): pnpm 9.7
[Compare Source](https://togithub.com/pnpm/pnpm/compare/v9.6.0...v9.7.0)
#### Minor Changes
- Added pnpm version management. If the `manage-package-manager-versions` setting is set to `true`, pnpm will switch to the version specified in the `packageManager` field of `package.json` [#8363](https://togithub.com/pnpm/pnpm/pull/8363). This is the same field used by Corepack. Example:
```json
{
"packageManager": "pnpm@9.3.0"
}
```
- Added the ability to apply patch to all versions [#8337](https://togithub.com/pnpm/pnpm/pull/8337).
If the key of `pnpm.patchedDependencies` is a package name without a version (e.g. `pkg`), pnpm will attempt to apply the patch to all versions of the package. Failures will be skipped. If there's only one version of `pkg` installed, `pnpm patch pkg` and subsequent `pnpm patch-commit $edit_dir` will create an entry named `pkg` in `pnpm.patchedDependencies`. And pnpm will attempt to apply this patch to other versions of `pkg` in the future.
- Change the default edit dir location when running `pnpm patch` from a temporary directory to `node_modules/.pnpm_patches/pkg[@version]` to allow the code editor to open the edit dir in the same file tree as the main project [#8379](https://togithub.com/pnpm/pnpm/issues/8379).
- Substitute environment variables in config keys [#6679](https://togithub.com/pnpm/pnpm/issues/6679).
#### Patch Changes
- `pnpm install` should run `node-gyp rebuild` if the project has a `binding.gyp` file even if the project doesn't have an install script [#8293](https://togithub.com/pnpm/pnpm/issues/8293).
- Print warnings to stderr [#8342](https://togithub.com/pnpm/pnpm/pull/8342).
- Peer dependencies of optional peer dependencies should be automatically installed [#8323](https://togithub.com/pnpm/pnpm/issues/8323).
#### Platinum Sponsors
#### Gold Sponsors
#### Our Silver Sponsors
### [`v9.6.0`](https://togithub.com/pnpm/pnpm/releases/tag/v9.6.0): pnpm 9.6
[Compare Source](https://togithub.com/pnpm/pnpm/compare/v9.5.0...v9.6.0)
#### Minor Changes
- Support specifying node version (via `pnpm.executionEnv.nodeVersion` in `package.json`) for running lifecycle scripts per each package in a workspace [#6720](https://togithub.com/pnpm/pnpm/issues/6720).
- Overrides now support the [`catalogs:` protocol](https://pnpm.io/catalogs) [#8303](https://togithub.com/pnpm/pnpm/issues/8303).
#### Patch Changes
- The `pnpm deploy` command now supports the [`catalog:` protocol](https://pnpm.io/catalogs) [#8298](https://togithub.com/pnpm/pnpm/pull/8298).
- The `pnpm outdated` command now supports the [`catalog:` protocol](https://pnpm.io/catalogs) [#8304](https://togithub.com/pnpm/pnpm/pull/8304).
- Correct the error message when trying to run `pnpm patch` without `node_modules/.modules.yaml` [#8257](https://togithub.com/pnpm/pnpm/issues/8257).
- Silent reporting fixed with the `pnpm exec` command [#7608](https://togithub.com/pnpm/pnpm/issues/7608).
- Add registries information to the calculation of dlx cache hash [#8299](https://togithub.com/pnpm/pnpm/pull/8299).
#### Platinum Sponsors
This PR contains the following updates:
9.4.0->9.7.0Release Notes
pnpm/pnpm (pnpm)
### [`v9.7.0`](https://togithub.com/pnpm/pnpm/releases/tag/v9.7.0): pnpm 9.7 [Compare Source](https://togithub.com/pnpm/pnpm/compare/v9.6.0...v9.7.0) #### Minor Changes - Added pnpm version management. If the `manage-package-manager-versions` setting is set to `true`, pnpm will switch to the version specified in the `packageManager` field of `package.json` [#8363](https://togithub.com/pnpm/pnpm/pull/8363). This is the same field used by Corepack. Example: ```json { "packageManager": "pnpm@9.3.0" } ``` - Added the ability to apply patch to all versions [#8337](https://togithub.com/pnpm/pnpm/pull/8337). If the key of `pnpm.patchedDependencies` is a package name without a version (e.g. `pkg`), pnpm will attempt to apply the patch to all versions of the package. Failures will be skipped. If there's only one version of `pkg` installed, `pnpm patch pkg` and subsequent `pnpm patch-commit $edit_dir` will create an entry named `pkg` in `pnpm.patchedDependencies`. And pnpm will attempt to apply this patch to other versions of `pkg` in the future. - Change the default edit dir location when running `pnpm patch` from a temporary directory to `node_modules/.pnpm_patches/pkg[@version]` to allow the code editor to open the edit dir in the same file tree as the main project [#8379](https://togithub.com/pnpm/pnpm/issues/8379). - Substitute environment variables in config keys [#6679](https://togithub.com/pnpm/pnpm/issues/6679). #### Patch Changes - `pnpm install` should run `node-gyp rebuild` if the project has a `binding.gyp` file even if the project doesn't have an install script [#8293](https://togithub.com/pnpm/pnpm/issues/8293). - Print warnings to stderr [#8342](https://togithub.com/pnpm/pnpm/pull/8342). - Peer dependencies of optional peer dependencies should be automatically installed [#8323](https://togithub.com/pnpm/pnpm/issues/8323). #### Platinum SponsorsConfiguration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
â™» Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.