v10.16.0
📦 pnpmView on GitHub →
✨ 3 features🐛 4 fixes🔧 6 symbols
Summary
This release adds a `minimumReleaseAge` safety setting and custom finder support, while fixing several bugs such as Node.js 24 deprecation warnings and improving error handling for `nodeVersion`.
Migration Steps
- Add `minimumReleaseAge` (e.g., `minimumReleaseAge: 1440`) to your `.npmrc` or `.pnpmrc` to enable the delay.
- If certain packages must bypass the delay, list them under `minimumReleaseAgeExclude` (e.g., `minimumReleaseAgeExclude:\n - webpack`).
- To use finder functions, define them in `.pnpmfile.cjs` under the `finders` export and invoke with `pnpm list --find-by=<function>` or `pnpm why --find-by=<function>`.
✨ New Features
- Introduced `minimumReleaseAge` setting to delay installation of newly released dependencies by a configurable number of minutes.
- Added `minimumReleaseAgeExclude` to whitelist packages that should ignore the release‑age restriction.
- Added support for custom finder functions (`finders`) that can be used with `pnpm list` and `pnpm why` via the `--find-by` flag.
🐛 Bug Fixes
- Fixed deprecation warning that was printed when running pnpm with Node.js 24.
- Now throws an error if `nodeVersion` is not set to an exact semver version.
- `pnpm publish` can now publish a `.tar.gz` file.
- Canceling a running process with Ctrl‑C now makes `pnpm run` return a non‑zero exit code.
🔧 Affected Symbols
minimumReleaseAgeminimumReleaseAgeExcludefindersnodeVersionpnpm publishpnpm run