v12.0.0-alpha.21
Breaking Changes📦 pnpmView on GitHub →
⚠ 1 breaking✨ 1 features🐛 1 fixes🔧 4 symbols
Summary
This release makes GitHub Actions dependency updates opt-in by default and improves how `pnpm update --latest` handles various dependency types. `pnpm setup` also now better integrates with GitHub Actions environments.
⚠️ Breaking Changes
- Previously, `pnpm update --latest` would overwrite dependency specifiers for `runtime:`, `git:`, `github:`, or remote tarball URLs with versions from unrelated packages found in the npm registry. This behavior has been corrected, and these dependencies will now be kept in their declared form. This might be a breaking change if you relied on the incorrect overwriting behavior.
Migration Steps
- To include GitHub Actions dependencies in `pnpm outdated` or `pnpm update`, use the `--include-github-actions` flag or set `update.githubActions` to `true` in `pnpm-workspace.yaml`.
✨ New Features
- `pnpm setup` now appends `PNPM_HOME` and the global bin directory to GitHub Actions environment files (`GITHUB_ENV` and `GITHUB_PATH`), enabling subsequent steps in the same job to run global commands like `pnpm add --global`.
🐛 Bug Fixes
- Checking GitHub Actions dependencies for updates is now opt-in for every command. `pnpm outdated` and `pnpm update` will not read workflow files unless `--include-github-actions` is passed or `update.githubActions` is set to `true` in `pnpm-workspace.yaml`. This resolves issues in environments where GitHub is not reachable as pnpm assumes (e.g., GitHub Enterprise Server, custom certificate authorities, or offline networks).